project and implimentation evaluator full report
Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
project report tiger
Active In SP
**

Posts: 1,062
Joined: Feb 2010
#1
26-02-2010, 04:30 PM



.doc   PROJECT EVALUATOR.doc (Size: 964 KB / Downloads: 65)

PROJECT EVALUATOR
By
GAYATHRI. K
PRATHIBHA.K.K
RAHNA P
MUHAMMED
ABSTRACT
The project and implimentation, PROJECT EVALUATOR is being designed to overcome the most of the manual processes that is going in a software firm. It is a web application that can simplify the task of the administrator, project and implimentation manager, project and implimentation leader, developer and tester. The process of accepting a project and implimentation from a client, assigning this project and implimentation to a project and implimentation leader in such a way that he is not overloaded, the task of division of the project and implimentation to various developers, daily evaluation of project and implimentation, weekly report of status of project and implimentation, testing and its report, all these functions was made easy with this project and implimentation.
Since Automatic generation of reports give complete details about the process that help to provide the information to the requester on the click of the mouse, so the project and implimentation leader and developers along with others could get the information at a button click. This will allow the office for speed - up the operations. The project and implimentation is designed in such a way that many of the input operations are done through well structured forms. The forms are capable of validating and checking the integrity and correctness of the input.
CONTENTS
SLNO CHAPTER PAGENO
1 INTODUCTION 1
2 OBJECTIVE AND SCOPE OF 3
PROJECT
3 TOOLS AND PLATFORM 6
3.1 MICROSOFT.NET
3.2 VB.NET
3.3 ASP.NET
3.4 INTRODUCTION TO SQLSERVER
¦3.5 WINDOWS 2000 SERVER
4 ORGANISATIONAL PROFILE 20
5. SYSTEM REQUIREMENT SPECIFICATION 23
5.1 HARDWARE SPECIFICATION
5.2 SOFTWARE SPECIFICATION

6 SYSTEM ANALYSIS 26
6.1 INTRODUCTION
6.2 STUDY OF EXISTING SYSTEM
6.3 DRAWBACK OF EXISTING
6.4 STUDY OF PROPOSED SYSTEM
6.5 ADVANTAGES OF PROPOSED SYSTEM
7 SYSTEM DESIGN 30
7.1 MODULARISATION CRITERIA
7.2 INPUT DESIGN
7.3 OUTPUT DESIGN
7.4 DATABASE DESIGN
7.5 DFD
8 SYSTEM TESTING 50
8.1 INTRODUCTION
8.2 TESTING TECHNIQUES
8.3 TESTING METHODOLOGIES
8.4 QUALITY ASSURANCE
9 IMPLEMENTATION 57
9.1 EQUIPMENT INSTALLATION
9.2 SYSTEM CHANGE OVER PLAN
9.3 WORKING OF SYSTEM
9.4 MAINTAINENCE
10 SCREENSHOTS 62
11 CONCLUSION 80
12 BIBILOGRAPHY 82
13 TABLES 39
1.
INTRODUCTION
The development of science and Technology is so rapid that the existence of the entire mankind is dependent on the implementation of scientific knowledge. Entire world is paying much attention to improve its life style by synthesizing the result of gaining the classical as well as modern knowledge. It is under these circumstances that computerization becomes relevant.
The competitiveness of the industrial scenario compels all the organizations to evolve ways and means to keep its operational efficiency at its peak to service. To achieve this, the integration of the operational domain of the organization is essential given the complexity of functions changing the market condition, migration of functional personnel and competition from parallel players make this task even more difficult.
Speeding of the business by cutting short cycle time by maintaining costs and improving quality is the greatest challenge of the industry. Manufacturing is at cross roads today. To respond to the pressure, the organization should have control, flexibility and integration of systems, functions and communication with in the system.
CXBJEClWE J4!MD SCCKFE 0<F (PROJECT
2. OBJECTIVE AND SCOPE OF THE PROJECT
The project and implimentation named 'Project Evaluator' is a web application that can be used for managing and monitoring various activities related to the project and implimentations in an organization.
A project and implimentation is a multitask job and its successful completion depends on the co¬operative works of many people. We all know that software is developed through a series of steps. That includes analysis, design, coding, testing and implementation. The proposed system is able to help in the development process through the entire life cycle.
The users of the proposed system can be administrator, project and implimentation leaders or developers. Administrator has the overall control of the organization activities. He is person who has the full rights including the management of employees, clients, project and implimentations etc. Administrator assigns project and implimentations to the project and implimentation leaders. A project and implimentation leader in turn divides project and implimentation into various modules and categorize various jobs and assign it to developers. Currently all these functions are done manually. In this fast growing business world it will be a great problem. In order to avoid such difficulties in the organization the proposed system can be used.
There are mainly FOUR modules in the system.
1. Administration Tasks
2. Project Leader Tasks
3. Developer Tasks
4. Tester Tasks
1. ADMINISTRATION TASKS
The administration tasks deals with the total administration of the software development in the company. It is done by the administrator in the organization. The administrator is able to control all the activities in the organization.
2. PROJECT LEADER TASKS
The project and implimentation leader tasks handle all the information of the scheduling of the job to the developers. The project and implimentation leader decides the schedules. The developers are given a particular time schedule to complete their job in the project and implimentation. The project and implimentation leader also does the performance monitoring of each developer. The project and implimentation leader will report the activities of each project and implimentation to the administrator in a particular period.
3. DEVELOPER TASKS
The developer has to know all the jobs assigned to the him and update the daily activities, delay details etc.
4. TESTER TASK
The tester does the task assigned to him by the project and implimentation leader and the administrator. Administrator assigns the task of creation of SRS and Test plan. The project and implimentation leader get a chance to monitor the works of the tester
"TOOLS JWD (PLMFOqtyl
3. TOOLS AND PLATFORM
3.1 Microsoft .NET
Microsoft .NET is software that connects information, people, systems, and devices. It spans clients, servers, and developer tools, and consists of: The .NET Framework 1.1, used for building and running all kinds of software, including Web-based applications, smart client applications, and XML Web services”components that facilitate integration by sharing data and functionality over a network through standard, platform-independent protocols such as XML (Extensible Markup Language), SOAP, and HTTP.
Developer tools, such as Microsoft Visual Studio .NET 2003 which provides an integrated development environment (IDE) for maximizing developer productivity with the .NET Framework.
A set of servers, including Microsoft Windows Server 2000, Microsoft SQL Server„¢, and Microsoft BizTalk Server, that integrates, runs, operates, and manages Web services and Web-based applications.
Client software, such as Windows XP, Windows CE, and Microsoft Office XP, that helps developers deliver a deep and compelling user experience across a family of devices and existing products.
What Is the .NET Framework
The .NET Framework is an integral Windows component for building and running the next generation of software applications and Web services. The .NET Framework: Supports over 20 different programming languages. Manages much of the plumbing involved in developing software, enabling developers to focus on the core business logic code. Makes it easier than ever before to build, deploy, and administer secure, robust, and high-performing applications. The .NET Framework is composed of the common language runtime and a unified set of class libraries.
Common Language Runtime (CLR)
The Common Language Runtime (CLR) serves as the execution environment for the .NET Framework. The CLR is responsible for managing the compiled code of .NET applications, which can be written in different languages including VB, C#, Java, and Perl. The cross-language integration is achieved through the two major components of CLR: Intermediate Language and Metadata.
Intermediate Language (IL) is an assembly language that runs on almost any type of CPU. IL achieves this versatility by using stacks to handle functions that normally occur in registers. As managed code, IL is just-in-time (JIT) compiled when .NET applications are executed. JIT compilers convert IL into machine language that is specific to the host CPU. [During runtime, JIT compilers have the luxury of choosing stacks, registers or other stores to implement IL stacks.] Various JIT compilers are provided by the CLR, making it possible for different computer architectures to execute IL. Unlike other assembly languages, IL integrates high-level concepts which make CLR code more robust. As a high level language, IL is strongly typed and uses the ideas behind structured-exception handling, deployment support, and component interaction. Thus a range of software can run on the .NET Framework as long as the compiler can produce IL.
Metadata, the second component of the CLR, is a description of the implemented code. The Metadata is responsible for ensuring that the CLR executes the code securely. To prevent modules of software from breaking type definitions, Metadata stores information regarding classes, methods, and types. Registers are no longer required to keep track of information because relevant data is stored with the compiled code or IL. By housing information on classes and registrations, Metadata allows the CLR to function more efficiently since programs are less likely to get hung up on version and inheritance dependencies.
Class Libraries
Base classes provide standard functionality such as input/output, string manipulation, security management, network communications, thread management, text management, and user interface design features.
The ADO.NET classes enable developers to interact with data accessed in the form of XML through the OLE DB, ODBC, Oracle, and SQL Server interfaces. XML classes enable XML manipulation, searching, and translations. The ASP.NET classes support the development of Web-based applications and Web services. The Windows Forms classes support the development of desktop-based smart client applications.
Together, the class libraries provide a common, consistent development interface across all languages supported by the .NET Framework..
3.2 VB.Net
VB.Net is a language that has been developed from VB. The only feature lacking in VB was its Internet capabilities and when we are moving towards the third generation of the Internet, it becomes important to have strong Internet Programming capabilities for any programming language. The industry is focusing on critical distributed computing with web services capabilities. At this moment VB.NET is definitely a powerful tool to provide all these solutions in integrated environment of .NET technology. The major problems with VB 6.0, which has been creating troubles for VB developers for a long time.
Problems with VB 6.0
1. No capabilities for multithreading.
2. Lack of implementation inheritance and other object oriented features.
3. Poor error handling capabilities.
4. Poor integration with other languages such as C++.
5. No effective user interface for Internet based applications.
In VB.NET all these shortcomings have been eliminated. In fact VB gets the most extensive changes of any existing language in the Visual Studio suite.
SOME NEW FEATURES OF VB.NET
1. Full support for object oriented programming.
2. Structured error handling capabilities.
3. Access to .NET Framework.
4. Powerful unified Integrated Development Environment (IDE).
5. Inherent support for XML & Web Services.
6. Better windows applications with Windows Forms.
7. New Console capabilities ofVB.NET.
8. New Web capabilities with Web Forms.
9. Immense power of tools & controls (including Server Controls).
10. Interoperatibility with other .NET complied languages.
11. Better database programming approach with ADO.NET.
EXCEPTION HANDLING - AN IMPORTANT FEATURE
Exception handling is an in built mechanism in .NET framework to detect and handle run time errors. The .NET framework contains lots of standard exceptions. The exceptions are anomalies that occur during the execution of a program. They can be because of user, logic or system errors. If a user do not provide a mechanism to handle these anomalies, the .NET run time environment provide a default mechanism, which terminates the program execution.
VB.NET provides three keywords try, catch and finally to do exception handling. The try encloses the statements that might throw an exception whereas catch handles an exception if one exists. The finally can be used for doing any clean
up process.
3.3 ASP.NET
ASP.NET is a programming framework built on the common language runtime that can be used on a server to build powerful Web applications. ASP.NET offers several important advantages over previous Web development models:
¢ Enhanced Performance
ASP.NET is compiled common language runtime code running on the server. Unlike its interpreted predecessors, ASP.NET can take advantage of early binding, just-in-time compilation, native optimization, and caching services right out of the box. This amounts to dramatically better performance before you ever write a line of code
¢ World-Class Tool Support
The ASP.NET framework is complemented by a rich toolbox and designer in the Visual Studio integrated development environment. WYSIWYG editing, drag-and-drop server controls, and automatic deployment are just a few of the features this powerful tool provides.
¢ Power and Flexibility
Because ASP.NET is based on the common language runtime, the power and flexibility of that entire platform is available to Web application developers. The .NET Framework class library, Messaging, and Data Access solutions are all seamlessly accessible from the Web. ASP.NET is also language-independent, so you can choose the language that best applies to your application or partition your application across many languages. Further, common language runtime interoperability guarantees that
your existing investment in COM-based development is preserved when migrating to ASP .NET.
¢ Simplicity
ASP.NET makes it easy to perform common tasks, from simple form submission and client authentication to deployment and site configuration. For example, the ASP.NET page framework allows you to build user interfaces that cleanly separate application logic from presentation code and to handle events in a simple, Visual Basic -like forms processing model. Additionally, the common language runtime simplifies development, with managed code services such as automatic reference counting and garbage collection.
¢ Manageability
ASP.NET employs a text-based, hierarchical configuration system, which simplifies applying settings to your server environment and Web applications. Because configuration information is stored as plain text, new settings may be applied without the aid of local administration tools. This "zero local administration" philosophy extends to deploying ASP.NET Framework applications as well. An ASP.NET Framework application is deployed to a server simply by copying the necessary files to the server. No server restart is required, even to deploy or replace running compiled code.
Scalability and Availability
ASP.NET has been designed with scalability in mind, with features specifically tailored to improve performance in clustered and multiprocessor environments. Further, processes are closely monitored and managed by the ASP.NET runtime, so that if one misbehaves (leaks, deadlocks), a new process can be created in its place, which helps keep your applications constantly available to handle requests
¢ Customizability and Extensibility
ASP.NET delivers a well-factored architecture that allows developers to "plug-in" their code at the appropriate level. In fact, it is possible to extend or replace any subcomponent of the ASP.NET runtime with your own custom-written component. Implementing custom authentication or state services has never been easier.
¢ Security.
With built in Windows authentication and per-application configuration, you can be assured that your applications are secure.
¢ Language Support
The Microsoft .NET Platform currently offers built-in support for three languages: C#, Visual Basic, and Script. Language Compatibility
The differences between the VBScript used in ASP and the Visual Basic .NET language used in ASP.NET are by far the most extensive of all the potential migration issues. Not only has ASP.NET departed from the VBScript language to "true" Visual Basic, but the Visual Basic language itself has undergone significant changes in this release. The changes are designed to:
¢ Make the language more consistent by bringing together features of the language with similar purposes.
¢ Simplify the language by redesigning the features that made Visual Basic less than "basic."
¢ Improve readability and maintainability by redesigning features that hid too many important details from the programmer.
¢ Improve robustness by enforcing better practices, such as type-safe programming.
3.4 INTRODUCTION TO SQL SERVER
The Structured Query Language (SQL) comprises one of the fundamental building blocks of modern database architecture. SQL defines the methods used to create and manipulate relational databases on all major platforms.
SQL comes in many flavors. Oracle databases utilize their proprietary PL / SQL. Microsoft SQL Server makes use of Transact - SQL. However, all of these variations are based upon the industry standard ANSI SQL.
SQL commands can be divided into two main sub languages. The Data Definition Language (DDL) contains the commands used to create and destroy databases and database objects. After the database structure is defined with DDL, database administrators and users can utilize the Data Manipulation Language to insert, retrieve and modify the data contained within it.
SQL Server 2000 is a powerful tool for turning information into opportunity. Industry leading support for XML, enhanced tools for system management and tuning, and exceptional scalability and reliability make SQL Server 2000 the best choice for the agile enterprise.
Features of SQL Server 2000
¢ Internet Integration: The SQL Server 2000 database engine includes integrated XML support. It also has the scalability, availability, and security capabilities in Web applications.
¢ Scalability and Availability: The same database engine can be used across platforms ranging from laptop computers running Microsoft Windows 98 through large, multiprocessor servers running Microsoft Windows 2000 Data Center Edition. SQL Server 2000 Enterprise Edition supports features such as federated servers, indexed views, and large memory support that allow it to scale to the performance levels required by the largest Web sites.
¢ Replication: With SQL Server 2000 we can implement merge, transactional, and snapshot replication with heterogeneous systems.
¢ Enterprise - Level Database Features: The SQL Server 2000 relational database engine supports the features required to support demanding data processing environments. The database engine protects data integrity while minimizing the overhead of managing thousands of users concurrently modifying the database. SQL Server 2000 distributed queries allow you to reference data from multiple sources as if it were a part of a SQL Server 2000 database, while at the same time, the distributed transaction support protects the integrity of any updates of the distributed data. Replication allows you to also maintain multiple copies of data, while ensuring that the separate copies remain synchronized.
¢ Ease of installation, deployment, and use: SQL Server 2000 includes a set of administrative and development tools that improve upon the process of installing, deploying, managing, and using SQL
¢ Server across several sites. SQL Server 2000 also supports a standards -based programming model integrated with the Windows DNA, making the use of SQL Server databases and data warehouses a seamless part of building powerful and scalable systems. These features allow you to rapidly deliver SQL Server applications that customers can implement with a minimum of installation and administrative overhead.
¢ Data warehousing & Data Mining. SQL Server 2000 includes tools for extracting and analyzing summary data for online analytical processing. SQL Server also includes tools for visually designing databases and analyzing data using English - based questions. Discover patterns and trends with data mining, and make predictions about future trends in business instances.
¢ Simplified Database Administration Automatic tuning and maintenance features enable administrators to focus on other critical tasks.
3.5WINDOWS 2000 SERVER
Windows 2000 Server includes improved network, application, and Web services. It provides increased reliability and scalability, lowers your cost of computing with powerful, flexible management services, and provides the best foundation for running business applications. Some features of Windows 2000 Server are given below.
New features for performance, security, and ease of management Server reliability
Increased reliability is the most critical design goal of the Windows 2000 Server release. The system offers you the following capabilities, helping provide increased levels of reliability: Improved memory management
Improved memory management means greater speed, reliability, and flexibility for your servers.
More robust system architecture
A robust system provides you with greater reliability even if one application or service encounters problems. Better diagnostic tools
You can monitor systems states and prevent problems more easily with better diagnostic tools. Recovery Console
With the Recovery Console, you can start a command-line console on a system on which a software problem (such as a problem with drivers or files) is preventing the system from starting. From the Recovery Console, you can use basic commands to try to recover the system. Windows File Protection
In Windows 2000, Windows File Protection prevents the replacement of protected system files, such as .sys, .dll, .ocx, .ttf, ion and .exe files used by the operating system. Windows File Protection runs in the background and prevents other programs from changing the files needed by the operating system.
Enhanced Backup utility
With Windows 2000 Server, you can back up data to a wide variety of storage media, such as tape drives, external hard disk drives, Zip disks, and recordable compact disks.
Server availability
Windows 2000 Server provides new features that dramatically increase system availability for your critical business solutions. With Plug and Play, planned system restarts are reduced by more than 90 percent. The system also gives you advanced fault tolerance and file system recoverability features. Fewer server restarts
Windows 2000 Server makes configuring hardware and software easier and dramatically reduces the number of times you must restart the system. Examples of activities you can accomplish without restarting the server include (but are not limited to):
Extending a storage volume Configuring network protocols Managing storage dynamically
Reconfiguring settings on PCI and other Plug and Play hardware Plug and Play
With Plug and Play, a combination of hardware and software support, the server can recognize and adapt to hardware configuration changes automatically, without your intervention and without restarting.
Hardware scalability
By choosing from products in the Windows 2000 Server family, you can take advantage of the growing number of competitively priced 2-, 4-, 16-, and 32-way multiprocessor computers, using ever-faster hardware technology.
Process Accounting for Web applications or sites
With Process Accounting, you can obtain information about how Web sites use CPU resources. This information can be crucial for making decisions about changing or improving hardware or applications. It can also be important when monitoring or diagnosing problems with scripts or applications. HTTP compression
HTTP compression conserves bandwidth and provides faster transmission of pages between the Web server and compression-enabled clients. Internet Explorer 4 and Internet Explorer 5 both support the compression methods used in Windows 2000 Server.
Predictable, end-to-end Quality of Service
Windows Quality of Service (QoS) allows you to control how applications are allotted network bandwidth. Important applications can be given more bandwidth, less important applications less bandwidth. QoS-based services and protocols provide a guaranteed, end-to-end, express delivery system for information across the network
Internet Authentication Service
IAS provides you with a central point for managing authentication, authorization, accounting and auditing of dial-up or VPN users. IAS uses the Internet Engineering Task Force (IETF) protocol called Remote Authentication Dial-In User Service (RADIUS).
Additional security features
Windows 2000 includes a variety of features for creation of a strong, flexible security system, including file encryption and the security features built into Active Directory
Encrypting File System
The Encrypting File System (EFS) in Windows 2000 complements existing access controls and adds a new level of protection for your data. The Encrypting
File System runs as an integrated system service, making it easy for you to manage, difficult to attack, and transparent to the user.
Flexible, secure authentication and authorization
Flexible and secure authentication and authorization services provide protection for data while minimizing barriers to doing business over the Internet.
Internet Protocol Security
; You can use Internet Protocol Security (IPSec) to secure communications within an intranet and to create secure Virtual Private Network solutions across the Internet. IPSec was designed by the Internet Engineering Task Force (IETF) and is an industry standard for encrypting TCP/IP traffic.
ORGANIZATION mOTILE
4.
ORGANIZATION PROFILE
RISCE SYSTEMS (P) Ltd
Research in Software Cryptology & Embedded (RISCE) Systems is the Information Technology consultancy and software development arm of BSOFT, a company that has been providing Network Infrastructure development and consultancy services in enterprise class networking to customers worldwide for over
a
decade.
Managed and staffed by IT professionals who have years of cross platform experience, RISCE has what it takes to deliver break-through solutions in Software Development, Project Management, System Architecture Design, Database Design, System Administration, Business Process Improvement, Enterprise Resource Planning, Embedded Technologies, Web Technologies, Database Warehousing, Wireless Applications, e-Government and e-Commerce.
As an outsourcing partner, RISCE brings world-class processes and global expertise in application development, in conformity with industry best practices, so as to enhance the value of application portfolio and help to ride the crest of every successive wave of technological advancement.
RISCE ensures proper requirements capture and evaluation, continuous project and implimentation monitoring and regular reporting to achieve the multiple objectives of reduced cycle times, speedy product delivery, lower cost of ownership, better risk mitigation and faster return on investment to clients.
The portfolio of reusable frameworks and components can be adapted to suit clients' requirements with minimum customization, so that they do not have to re¬invent the wheel every time. This ensures speedy product delivery and faster time to market. Our unflinching commitment to continuous process improvement and our holistic approach to quality will ensure measurable benefits to our clients by way of cost savings, productivity increases and speed in achieving business goals.
5. SYSTEM REQUIREMENT SPECIFICATION
5.1 Hardware Specification
Requirements vary for different combinations of components within Visual Studio .NET 2003. Review the table below to determine the minimum system requirements for running Visual Studio .NET 2003.
Hardware Requirements and Recommendations
Hardware Component Requirement Recommendation
BBHhHHBR - Jfe
Processor Intel Pentium class, 600 ¦ Higher megahertz (MHz)
RAM 128 MB 256 MB
¦
; Free hard disk space 370 MB (minimum 600 MB install)
Monitor VGA Super VGA
; CD-ROM drive 24X 52X
| Mouse Standard

Keyboard
Standard
.2 Software Specification
Application Type : Web
Technology Used : ASP.NET
Language Used : VB
Back End : SQL Server 2000
Operating System : Windows 2000 or above
SYSTEM ANALYSIS
6. SYSTEM ANALYSIS
6.1 INTRODUCTION
System analysis is the process of gathering and interpreting facts, diagnosing problems and using the information to recommend improvements on. the system. System analysis is a problem solving activity that requires intensive communication between the system users and system developers.
System analysis or study is an important phase of any system development process. The system is studied to the minutest detail and analyzed. The system analyst plays the role of an interrogator and dwells deep into the working of the present system. The system is viewed as a whole and the inputs to the system are identified. The outputs from the organization are traced through the various processing that the inputs phase through in the organization.
.2 STUDY OF THE EXISTING SYSTEM
The existing system was completely a manual process in which the administrator, project and implimentation leader and developer has to perform all their functions manually. This leads to an inconsistent delay to the clients and also the queries related to project and implimentation progress etc cannot be answered easily.
In the existing system, it is very difficult to maintain the details of entities in the organization. All the details are entered in the form of hard copies, which consumes a lot of time and skilled manpower. There is no provision for the validation of data that is being entered that is if the user enters some data that is not valid, there is no provision for rectifying the errors. There are chances for misplacing of importance details and files containing crucial data. This will lead to loss of data. The present system is not user friendly; all the work is done manually and is tiring for the user. All the operations are mainly performed by hand with the aid of basic tools such as paper, pen etc.
6.3 DRAWBACKS OF EXISTING SYSTEM
The existing system is manual, which is quite tedious and time consuming.
¢ Delay in processing the information.
¢ Users getting exhausted which leads to errors and omissions.
¢ Large piles of papers were maintained to keep the daily work details.
¢ Since it is a manual system, it is prone to lot of errors.
¢ Updating of records is very difficult and time consuming.
¢ Viewing of particular record leads to searching of the bulk of reports being maintained.
These problems will lead to delay, which is not expected by any clients. In order to overcome these disadvantages the manual system was decided to be automated which pursue with a front end user interface which has a variety of choices to the users.
6.4 STUDY OF THE PROPOSED SYSTEM
Defining the Problem
The disadvantages of existing system has been solved by automating the Project Evaluator .Since this is a web application the user may get information by the click of mouse. Administrator, project and implimentation leader and developer can perform their functions systematically and quickly.
6.5 ADVANTAGES OF THE PROPOSED SYSTEM
¢ The proposed system is supposed to automate much of the manual procedures and functions.
¢ This will allow the office for speed - up the operations.
¢ The proposed system is designed in such a way that many of the input operations are done through well structured forms.
¢ The forms are capable of validating and checking the integrity and correctness of the input.
¢ Automatic generation of reports give complete details about the process that help to provide the information to the requester on the click of the mouse.
SYSTEM c&ESiqN
7. SYSTEM DESIGN
System design is a solution, a "how to "approach to the creation of a new system. This important phase is composed of several steps. It provides the understanding and procedural details necessary for implementing the system. Emphasis is on translating the performance requirements into design specifications. It translates the system requirements into ways of operational zing them.
7.1 MODULARISATION CRITERIA
Modularization allows the designers to decompose a system into functional units to impose hierarchical ordering or function usage, to implement data abstractions, and to develop independently useful subsystems. In addition modularization can be used to isolate machine dependencies to improve the performance of software product, or to ease debugging, testing integration, tuning and modification of the system.
The project and implimentation entitled 'Project Evaluator' contains three modules: Administration tasks, Project leader tasks and Developer tasks. The administration tasks deals with the total administration of the software development in the company. It is done by the administrator in the organization. The administrator is able to control all the activities in the organization. The project and implimentation leader tasks handle all the information of the scheduling of the job to the developers. The project and implimentation leader decides the schedules. The developers are given a particular time schedule to complete their job in the project and implimentation. The project and implimentation leader also does the performance monitoring of each developer. The project and implimentation leader will report the activities of each developer to the administrator at the end of each day's work. The developer has to know all the jobs assigned to the him and update the daily activities, delay
details etc.
Administrative Tasks
¢ Handle Employee Database
¢ Handle Client Information
¢ Handle Project Details Database
¢ Handle Shift details
¢ Assign project and implimentations to Project Leader
¢ Monitor Project status
Project Leader Tasks
¢ Handle Team details
¢ Handle Job Details
¢ Handle Module Details
¢ Assign Jobs to Developers
¢ Reports to Project Manager
¢ Handle Daily Activities and Delay details
Developer Tasks
¢ View Job details
¢ Update Daily Activities
¢ Update Delay Details
TESTER Tasks
¢ Create SRS
¢ Create Test Plan
¢ Create Test Report
7.2 INPUT DESIGN
Inaccurate input data are the most common cause of errors in data processing. Errors entered by data entry operators can be controlled by input design. Input design is the process of converting user-originated inputs to a computer-based format. In the system design phase, the expanded data flow diagram identifies logical data flows, data stores, sources and destinations. Input data are collected and organized into groups of similar data. Once identified, appropriate input media are selected for processing.
Input design shows how user-oriented input is converted to a computer-based format. The goal of designing input data is to make data entry as easy, logical and free from errors as possible. Input design is the part of the overall system design, which requires very careful attention. If the data going into the system is incorrect then the processing and output will magnify these errors.
The design decisions for handling input specify how data are accepted for computer processing. Analysts decide whether the data are entered directly, or by using source documents. The quality of system describes the manner in which data enter the system for processing. It ensures the reliability of the system and produce results from accurate data.
The main focus is on the following:
¢ Effectiveness
¢ Accuracy
¢ Ease to use
¢ Consistency
¢ Simplicity
¢ Attractiveness
All these objectives are important and can be attained by the use of basic design principles.
Several activities are to be performed for the overall input process. They include some of the following:
¢ Data recording from its source
¢ Data conversion to computer acceptable medium
¢ Data validation
¢ Data flow control
¢ Data correction if necessary
The nature of input data is determined partially during logical system design. However the nature of inputs is made more explicit during the physical design. The impact of inputs on the system is also determined.
Effort has been made to ensure that input data remains accurate from the stage at which it is recorded and documented to the stage at which it is accepted by the computer.
Controls such as pop up lists and combo boxes are used to enable the user to know the exact bounds of input data. Thus these controls ensure that inputs are accepted only from a valid range. Validation procedures are also present to detect errors in data input, which is beyond control procedures. Validation procedures are designed to check each record, data item or field against certain criteria.
Input Design in Project Evaluator
¢ Proper validation on each and every textbox, drop down list have been done in order to generate user friendly error messages like check of null values, empty check, change case checks, unwanted space removal between the text, check numeric etc.
¢ All the user interface are collections of drop down lists which helps to load details about the employee types,department,designation etc which are separately maintained in the database, which helps the user to just select from the list rather than entering the data into it.
7.3 OUTPUT DESIGN
Computer output is the most important and direct source of information to the user. Efficient, intelligible, output design should improve the system's relationships with the user and help in decision making. Users generally merit the system solely by its output. Hence the system analysts work closely with users through an interactive process, until the result is considered to be satisfactory.
The output design is an ongoing activity almost from the beginning of the project and implimentation, and follows the principles of form design. The primary considerations in the design of the output are the requirement of the information and the objectives of the end users. A major form of output is a hard copy from the printer, however soft copies are also available.
A major form of output is a hard copy obtained from the printer. These printouts are designed to include the exact requirements of the user. The outputs required by the end user are defined during the logical design stage in terms of:
¢ The type of output.
¢ The content.
¢ The format.
¢ The action required.
Objective of the output design
¢ Design output to serve the intended purposes.
¢ Design output to fit the user requirements.
¢ Deliver the appropriate quantity of output.
¢ Ensure that output is exactly what is required.
¢ Provide output on time.
¢ Choose the right output method.
Output Design in Project Evaluator
¢ The details about the existing employees, project and implimentations, clients etc can be viewed by browsing through the web pages by clicking appropriate links which gives a clear output about the existing status.
¢ Data grids used as user interface helps to know the proper insertion, updation and deletion of records to the tables.
7.4 DATABASE DESIGN
A database is an organized mechanism that has the capability of storing information through which a user can retrieve stored information in an effective and efficient manner. The data is the purpose of any database and must be protected.
The database design is a two level process. In the first step user requirements are gathered together and a database is designed which will meet these requirements as cleanly as possible. This step is called Information Level Design and it is taken independent of any individual DBMS.
In the second step this information level design is transferred in to a design for the specific DBMS that will be used to implement the system in question. This step is called Physical Level Design, concerned with the characteristics of the specific DBMS that will be used. A database design runs parallel with the system design. The organization of the data in the database is aimed to achieve the following two major objectives.
¢ Data Integrity
¢ Data Independence
Normalization is the process of decomposing the attributes in an application, which results in a set of tables with very simple structure. The purpose of normalization is to make tables as simple as possible. Normalization is carried out in this system for the following reasons.
¢ To structure the data so that there is no repetition of data, this helps in
saving-space.
¢ To permit simple retrieval of data in response to query and report request.
¢ To simplify the maintenance of the data through updates, insertions and deletions.
¢ To reduce the need to restructure or reorganize data when new application requirements arise.
Primary Key is assigned for this purpose. The primary key fields in almost all the tables help to ease the search and improve efficiency. The proposed system is using second normal form as it is found most suitable. In second normal form each row must contain associated field that describes an attribute of the entry that the table describes.
Database Design in Project Evaluator
¢ All the tables have been uniquely identified by a key called primary key.
¢ To avoid redundancy of code more than one Foreign Keys has been used to link couple of tables.
¢ Usage of views and database diagrams has helped to set relationship with one or more tables and reduce redundancy.
¢ Insertion, Updation and Deletion into a table from the front end have been performed by using the primary and foreign key constraints.
7.4.1 TABLES
Daily activity
Column Name Data Type | Length Allow Nulls
IdailyactivityidH int 4
ernpluyeeid varchar 10
daydate datetime 8 V
jobcode varchar 10
workdescription varchar 200 V
'status int 4
Delay
-olumn Name Data Type | Length | Allow Nulls
mid lid
ddate reason int int int
datetime nvarchar
4 4 4
8
2000
Department
(.olumn Name Data Type | Length | Allow Nulls
.JS33E int 4
deptname varchar 10 s/
description varchar 500 V
Designation
Column Name Data Type [Length Allow Nulls
EesianationidM nchar 5
designationname varchar 50
description varchar 100 V
Workstation status
Column Name Data Type |Length Allow Nulls
BMorkstatusidM int 4
project and implimentationleaderid int 4 \f
workstationid int 4 V
, project and implimentationed int 4 V
statusid int 4 V
Employee official
Column Name Data Type Length Allow Nulls
int 4
empname char 100
workstation int 4 V
deptid int 4
designationid int 4
password nvarchar 50
experience int 4 V
salary nvarchar 10
Employee personnel
Column Name | Data Type | Length Allow Nulls |
'ji'iUM int 4
ernpname varchar
sex char 10
education varchar 25 V
dateofbirth datetirne u
dateofjoinig datetime V
dateofleaving datetirne o V
address varchar 100
phone int 4 V
email .nchar ¦-¢rr V
Job details
Column Name Data Type Length Allow Nulls
Ml int 4
io be ode int 4
muduledetailid int 4
employee id int 4
shiftid , int 4
Module details
Column Name Data Type |Length Allow Nulls
I rnoduleidH int 4
modulename varchar 25 V
description varchar 200
project and implimentationid int 4
phaseid int 4
startdate datetirne 8 V
enddate datetirne 8 V
Password
Column Name | Data Type | Length | Allow Nulls
m int 4
emptype int 4
password varchar 50
Phase details
Column Name | Data Type | Length | Allow Nulls
int 4
phasename varchar 15 V
i description char 100 v
Project Details
Shift details
column Name Data Type Length Allow Nulls
USES int 4
shiftname varchar 15 V
description varchar 200 V
frorntirne datetime 3
totime datetime 8
SRS assigning
Column Name Data Type | Length | Allow Nulls
int 4
srsname varchar 50
clientid int 4
project and implimentationid int 4
designation varchar 50
.employeeid int 4
SRS uploading
Column Name Data Type Length Allow Nulls
3Efti| int 4
empid int 4
project and implimentationid int 4
srsfile varchar 50
Test plan assigning
Column Name Data Type Length Allow Nulls
int 4
testname nvarchar 50
'project and implimentationid int 4
¦empid int 4
Test Plan uploading
Column Name | Data Type | Length | Allow Nulls
y ItesrnlanidM int 4
empid int 4
project and implimentationid int 4
¦testfile varchar 50
Test Report
Column Name Data Type Length | Allow Nulls
Eestreoortidl int 4
empid int 4
pid int 4
testreportname varchar 50
testreport nvarchar 2000
Workstation
Column Name Data Type Length Allow Nulls
IworkstationidB int 4
workstationname varchar 50
| description varchar 350 V
7.5
DFD
Basic DFD symbols:
To construct a Data Flow Diagram, we use
¦ ¢ Arrow
¦ ¢ Circles
¢ Open End Box
¢ Squares
Arrow-n arrow identifies the data flow in motion. I is a pipeline through which information is flown like the rectangle in the Flow Chart
Data may flow a source to a processor and from a data store or process.An arrow line depicts the flow, with the arrow head pointing in the direction of flow.
Circle- Circle stands for process that converts the data into information
A process that represents transformation where incoming data flows is changed into outgoing flows.
Rectangle- A rectangle defines a source or destination of system data.
A source is a person or a part of an organization, which enters, or receives information from the system but is considered to be outside the context of the data flow model.
A data store is a responsibility of data that is to be stored for use by one or more process, which may be as simple as buffer or sophisticated as relational database. A graphical picture of the logical steps and sequence involved in a procedure or a program is called a flow chart.
Unlike detailed flow Chart, Data Flow Diagram does not supply detailed description of the modules but graphically describes a system's data and how the data interact with the system. Six rules for considering the Data Flow Diagram
1. Arrows should not cross each other
2. Squares, circles and files must bear names
3. Decomposed data flow squares and circles can have the same names.
4. Choose meaningful names for data flow
5. Draw all data flows around the outside of the diagram.
6. Control information such as record count, passwords, and validation
requirements are not pertinent to Data Flow Diagram
Open End Box-An Open End Box represents a data store, data at rest or temporary reposition of data.
Level 0
User/ Emp
User/emp

w
LEVEL 1 DFD
LEVEL 2: ADMIN
LEVEL 2: PROJECT LEADER
DATAFLOW DIAGRAM
DEPARTMENT
DESIGNATION
CLENTMASTER
LEVEL 2:
EMPPERSOHNEL V,,
*T
EMPOFFICIAL
del
View Reports itaik^-^ details
SWFTMASTER
login
V,.
PROJECT LEADER
'details
W Login "\ / Create
^ Checking [ ^taSs .'jobs&Assign r_
login
Update \ Project *. Progress ;
3.5 /
Invalid 3 1 to teams f
I TEAM / f\ 33 y\ \details
i£WP OFFICIAL
JOBMASTER
JOBDETAIL S
Daily *\
DEI/EL-OPER
stalls
PPJLDR/ I ADMIN
DAILY ACTIVITY
~"1'Entries&belay\ A 1 Details /”"'17: details 1 34
SYSTEM TESTlNg
8. SYSTEM TESTING
8.1 INTRODUCTION
Software testing is the crucial element of the software quality assurance and represents the ultimate review of specification, design and coding. Testing represents an interesting anomaly for the software. During earlier definitions and development phases, it was attempted to build software from an abstract concept to tangible information. The testing phase is a very important phase since it is in this phase; we make sure that the system will perform the task without any error. Testing is vital to the success of the system and is being done by classifying it in two ways- System Testing and Program Testing. Program Testing involves checking the syntax and logic of the program. This checking resulted in achieving error free programs.
No matter how carefully a programmer designs and plans application, the programs are sure to have a few bugs in them. Errors in the program immediately stop program execution and display an error message if the errors are syntax errors. After debugging one can identify the limitations of this project and implimentation and hence corrections are made. During the system development, each source code was tested for its level of correctness. Each form was run a number of times in order to ensure that the details are entered correctly and works properly.
8.2 TESTING TECHNIQUES
Computer software considers two types of test cases as one to test the specific function of the product called black box testing and other to test the internal working of the product called as white box testing.
Black Box Testing
Black- box testing is done in this project and implimentation, which proves that the software functions are operational that input is properly accepted and output is correctly produced and integrity of external information is maintained.
¢ The software is tested for finding errors.
¢ Incorrect or missing functions are identified and corrected.
¢ Interface errors are checked and corrected
Black box testing examines some functional aspects of a system with little regard for the internal structure of the software.
White Box Testing
White-box testing of software is predicted on close examination of procedural details. Logical paths through the software are tested by providing test cases that exercises specific set of conditions and/or loops. Using white-box testing methods, the test cases designed for this system are:
¢ Guaranteed that all independent paths within a module have been exercised at least once.
¢ Exercised all logical decisions on their true and false sides.
¢ Exercised all loops at their boundaries and within their operational bounds.
¢ Exercised internal data structure to assure their validity.
These test cases are applied to achieve more complete testing by uncovering and correcting the highest number of errors in a program.
8.3 TESTING METHODOLOGIES
¢ Unit Testing
¢ Validation Testing
¢ Output Testing
¢ User Acceptance Testing
Unit Testing
Unit testing focuses verification efforts on the smallest unit of software design, the module. This is also known as "Module Testing". The modules are tested separately. This testing is carried out during programming stage itself. In this testing step each module is found to be working satisfactorily as regard to the expected output from the module. This test can be considered as unit test. This has been carried out after the completion of one complete part. The word validation itself says about the nature of the test. Entire controls in the program have been tested in this manner. The limitations, nature and the boundaries are tested during the test. This test makes the work worthy to be developed further.
Validation Testing
Validation testing is where requirements established as a part of software requirement analysis is validated against the software that has been constructed. This test provides the final assurance that the software meets all functional, behavioral and performance requirements. The errors, which are uncovered during integration testing, are corrected during this phase.
Output Testing
After performing the validation testing, the next step is output testing of the proposed system since no system could be useful if it does not produce the required output in the specified format. The output generated or displayed by the system under consideration is testing asking the users about the format required by them. Here, the output is considered into two ways: one is on the screen and the other is printed format.
The output format on the screen is found to be correct as the format designed according to the user needs. For the hard copy also, the output comes out as specified by the user. Hence output testing doesn't result in any connection in the system.
User Acceptance Testing
User acceptance of a system is the key factor for the success of any system. The system under consideration is tested for user acceptance by constantly keeping in touch with the prospective system users at time of developing and making for Project Evaluator system.
The testing of the software began along with coding. Since the design was fully object - oriented, first the interfaces were developed and tested. Then unit testing was done for every module in the software for various inputs, such that each line of code is at least once executed.
8.4 QUALITY ASSURANCE
Quality assurance includes formal review of care, problem identification, corrective actions to remedy any deficiencies and evaluation of actions taken. The goal of quality assurance is to provide management with the data necessary to be informed about product quality, thereby gaining insight and confide that product quality is meeting its goals. This is an "umbrella activity that is applied throughout the engineering process.
Software quality assurance encompasses
¦ Analysis, design, coding and testing methods and tools
¦ Formal technical reviews that are applied during each software engineering
¦ Multi-layered testing strategy
¦ Control of software documentation and the change made to it.
¦ A procedure to ensure compliance with software development standards.
¦ Measurement and reporting mechanisms.
The system is adaptability to new environment. It can be easily undergo changeover. Since it is an application system, the quality of the output is assured as long as the hardware doesn't have any complaint.
Quality Factors
The factors that affect the quality can be categorized into two broad groups:
¦ Factors that can be directly measured.
¦ Factors that can be indirectly measured
¦ These factors focus on three important aspects of a software product
¦ Its operational characteristics
¦ Its ability to undergo change
¦ Its adaptability to new environment.
IMPLEMENTATION
9. IMPLEMENTATION
Implementation is the process of converting a new or a revised system design into an operational one. There are 3 types of implementation:
1) Implementation of a computer system to replace a manual system. The
. problems encountered are converting files, training users, creating accurate
files, and verifying printouts for integrity.
2) Implementation of a new computer system to replace an existing one. This is usually a difficult conversion. If no t properly planned there can be many problems. Some large computer systems have taken as long as a year to convert.
3) Implementation of a modified application to replace an existing one, using the same computer. This type of conversion is relatively easy to handle, provided there are no major changes in the files.
9.1 EQUIPMENT INSTALLATION
Equipment installation is an activity that is completed during the development phase. The principle equipment related activities are: site preparation, equipment installation and hardware and software checkout.
9.2 SYSTEM CHANGE OVER PLAN
The conversion is the process of initiating and performing all of the physical operation that result directly in the turnover of the new system to the user. The objective is to put the tested system into operation while holding costs, risks and personnel irritation to a minimum. It involves (1) creating computer-
compatible files. (2) Training the operating staff and (3) installing terminals and hardware. A critical aspect of conversion is not disrupting the functioning of the
organization. System maintenance is needed to accommodate changes in the business environment due to the expansion of needs of the user in the coming times. It is also helpful in correcting the errors that may arise unseen in the system in the future. There are two parts to conversion:
1. A conversion plan, which is implemented throughout the development phase.
2. A changeover plan for moving the system from the development phase to operation phase.
The conversion plan includes procedure conversion, program conversion and file conversion. The changeover plan also specifies the method of changeover from the old to the new system. Choices of changeover methods include parallel operations and immediate placement of phased changeover. The latter usually is the recommended method.
The changeover takes place when:
¢ The system is developed and tested
¢ Users are satisfied with the results
There are many ways to in which change over may be achieved. Commonly used methods are the following:
¢ Direct changeover
¢ Parallel changeover
¢ Pilot running changeover
¢ Stages changeover
Occasionally the combinations of these methods are used. Parallel running changeover method is used in the implementation of the new system. The current data is processed both manually and by the new system and the results are crosschecked. The old manual system is kept alive and operational until the new system has been proved for at least one system cycle.
9.3 WORKING OF THE SYSTEM
A system can be said working properly only when it works perfectly in every area. The working of the proposed system can be evaluated by checking whether all objectives of the system have been well taken care of The proposed system is designed to eliminate all disadvantages of the existing system. It is designed keeping in mind all the drawbacks of the present system in order to provide a permanent solution to the existing system. The primary aim of the proposed system is to be speed up transactions. The preparation of all report and documents take less time since the verifications are done automatically.
Main objective of the system are:
¢ Speeding up operation.
¢ Improve accuracy of information.
¢ Reducing waiting time.
¢ Provide quick and up to date response.
¢ Reduce clerical work.
9.4 MAINTENANCE
Once the software is fully developed and implemented, the company starts to use the software. The company also grows and more divisions may be attached to the company, or the database of the company can grow in size. So after some time the software, which has been installed, needs some modification. If the software needs modification all the steps needed to develop new software has to be executed.
The need has to be studied, the design has to be made and coding has to be done. Then the new module has to be connected to the existing software modules.
Even if the software is working perfectly, we must to do routine testing and any new bug if detected, has to be fixed. No software ever developed will be bug free forever. When a new situation arises, the software can create an error, but if taken care of immediately the software will not be causing more problems.
Maintenance covers a wide range of activities, including correcting coding and design errors, updating documentation and test data, and upgrading user support.
sc^cENStfors
Department Of Computer Science & Engineering S N G C E
L
„¢*u i.rc acit-nin!str<ato
PASSWORD
¦STATUSm
STATUSNAME OPTION
STATUS NAME
progressing V*E~vvr/E-I
completed .hWEJlT
T
SUBMIT I CANCEL
P mitial jVIEW/ESrf
4 sta^nent fvtFA'T-">n'
¦j DONE
»J LOCAL MB-ANET
File E* View Favorites To* IJelp
WORKSTATION DETAILS
WORKSTATION ID WORKSTATION NAME
DESCRIPTION
WORKSTATION NAME DESCRIPTION OPTION
Ttochi ±e IT world of kerala ^L..l..JXiIi.
iTVM the technopark.keraia VTFW.'l''. i!
^Cheimai |TN VJI "
The IT center of India ¢Â¦¢
SUBMIT CANCEL " DELETE
*jj Locd intranet
J
Help
File £dit Vfc-w FovonVe-;
t Statu iWorwtaliun ! Depart rr.snt (Designator
iPhaseDsta^
M1LT1 ALUltK
fr%ht1 J
the first section of night s
07 00
DESCRIPTION
^Back ¢ ^ ^ * <. , ilM Favorite *g) j £*- §^ iS * jg ft 4fc ¢Â£j http;//kKalwsyevaKj^aH/adnwwre«.aspxid>-l
**Hrft"T
žVTž DESCRIPTION NAME FROMTLME -
TOTEME OPTION
, , 'first section of the
dayl May 1/1/1900 6:00 00 AM 1/1/1900 i
1 00:00 jVIEWffiDi:

AM
|
Ida 2 * C secon^
| jsection of the day 1/1/1900 1 00 00 AM
1/1/1900 7 00 00 AM 1/1/1900
7:00:00 ¦¦¦^¢fEJjV AM
L-., fthe first section of '^tshffi
1/1/1900
1 00 00 I'-TEW/FX'"

AM
SUBMIT I CANCEL || DELETE
' 'the second shift of 1/1/1900
,m ra$t 1 00 00 AM
L i
: i/i/i9oo-
=6:00:00 ;AM
Fife £<*t yjew Favorites look Hdp
¢ o siiift /¢¢*¢* ^>=<„¢*» es-ii^'....£i
‚¬il l^tp://kKatTost/evduatorH/admrnarea.aspxid-=l
PHASE DETAILS
PHASEID PHASE NAME
DESCRIPTION
PHASE NAME
esign coding
testing
DESC'HLPTiOr'
OPTION
*j Local intranet
:|ile Ed* Vjew Favorites Toots Help
^Back
F*tp://!oealhosr/evaluatorl4/adminare3 a-;pxid«l
ri!i>Ti«' ”'nwymw.11 „¢
TESTPLAN ASSIGNING
TEST TD ¦.
TEST NAME PROJECT NAME EMP NAME
3
testl ! Sngce
SUBMIT
CANCEL
4] Done
* ^ Local Intranet irrototl lntpnh:t i
MB
FJr frit "£iew Favorites look tJefci
©Back - Q ,») gj ^iPs-rd, ^frta*** ^»
& id ¢ B a. -3.
EMPLOYEE-PERSONAL DETAILS
EMPID
EMP NAME
SEX OMale OFemale i
-
EDUCATION DOB
DOJ DOt
PHONE E-MAIL
^¦j Local intranet
File £dt View Favorites loots Help
O " ' 0 13 liS ffc I P5^ ifrFavors -0 ¢ ^ f | ' ft 4&
r] !ocalhost/evJunior H/adnwiafe<3.ai[;x>id=l
SRS ASSIGNING FORM j
SRS ID
SRS NAME SISlj
CLIENT NAME SNGCE
PROJECT NAME Sngce
DESIGNATION tester
EMPLOYEE NAME pnya
Eite Edit View Favorites Tools Help
©w O >¦ | f, , *¢* 4
5 kxaN)^/evaluatc»-14/3diTiinaiea.a5pxid=l
sngce Ms srs3
Sngce Sngce RISCE
SRSIdac SRS2.doc
SRSS.dor
Local intranet
File E* View Favorites Tools Help
O8** ¢ ; »' f..'' P*»* 0- & » * uv* ii si
Hjj rtttp://localriost/evaluator 1 ¦Vadminatea. aspxid= 1
vj I^J Go
CHANGE PASSWORD
CURRENT PASSWORD
NEW PASSWORD
RETYPEPASSWORD
* j Local Intranet
liup.;;ioi..i.HI)ust/ev^lii,iion4acslpkndwTES"r20PLAN2.do<. - Microsoft lrituni«l tff^Ioier
01
TEST PLAN
People Responsible for Application
& ' 1
Test Le ad:
Tester:
Developer:
Developer lead:
Program manager:
Unknown Zone
P)L<*R».'rt MIC.TOJ-.OF! I H TEN IFF F EXPLORER
Fie Edit Sew Favorites lock Help
.^.YRR,.,FLOCAT»SY«»JLBAL>L</P)LARM.ASP>ID»;
MA A E
> * Station; 31 i< I.MB**^^BII
PROJECTNAME DESCRIPTION STARTDATE ENDDATE PLATFORM FRONTEND BACKEND
AM
5/12/2006
' 12:00:00-AM
the project and implimentation which 5(1/2006 6/29/2006
Sngce automates the i200 00 AM 1200:00 ASP.Net SQLSERVER2000 \
RISCE
XP
¦ASP.NEt
Sql
working of office
automationof s/w 5/1/2006 firm '\ 12:00:00 AM
R^JDONE
*i LOCAL INTRANET
t\ ^ ^ ' Search ^F«t« 0 g|.
Fife Edit F.v/
Add>*;s l-gj httpr/Axat»st/evaluatorl4/devek)pefarea.aspxld=3
DAILY ACTTVTITjES
DAILY ACnYiTY ID
lfc'12C06
I Click Alter Selecting Date JM
< May 2006 > j
Sun Mon Tue Wed Thu Fri Sat 1
WORK DESCRIPTION
I
doing the main sect ion
50|
22 3 4 5 6
1 8 9 10 11 12 13
14 15 16 17 18 19 20
21 22 23 24 25 26 27
28 29 30 31 1 2 3
4 5 6 7 8 9 10
I ,
*j Local rtranet
~ ! - l' L;l . %£T^»tt htteifibt cxploicr
File £dlt View Favorites look tfelp
¢ 0 :.*J (1 ^ /-Search ^Favonte 0 g. % S - L
: rAtp://locdho5t/evduacorl4/p|area.aspxid=2
Mocule Assign-imf
MODITLE DETAILS
MODULE ID MODULE NAME DESCRIPTION
PROJECT NAME
PHASE NAME START DATE END DATE
modi
analysing of evaluator
brigce analysis 6/2/2006 5a20C6
I START j : END
< May 2006 >
Sun Mon Tue Wed Thu Fn Sat 30 1 2 | 4 5 6 7 8 9 10 n. 12 j3 14 i'> j 1R 10 >n
* j Local intranet
Sngce
ml
DESCRIPTION STARTDATE
administration 5/1/2006 1200:00 AM
sf£]Done
*J Local tntr arret
File £dit Vtew F.avofites fools yelp
vjg) Go
TESTNAME s EMFLD: 4 PROJECTID : 1
TESTNAME s EMPLD: 4 PROJECTID : 11
^0 0°°*
Reply

Important Note..!

If you are not satisfied with above reply ,..Please

ASK HERE

So that we will collect data for you and will made reply to the request....OR try below "QUICK REPLY" box to add a reply to this page

Quick Reply
Message
Type your reply to this message here.


Image Verification
Please enter the text contained within the image into the text box below it. This process is used to prevent automated spam bots.
Image Verification
(case insensitive)

Possibly Related Threads...
Thread Author Replies Views Last Post
  Brain Chips full report seminar class 2 3,316 13-07-2016, 03:38 PM
Last Post: jaseela123
  Intranet Mailing System full report seminar tips 4 1,648 06-05-2016, 11:25 AM
Last Post: mkaasees
  WCPS Web Based Claims Processing System A PROJECT REPORT study tips 1 495 05-04-2016, 12:33 PM
Last Post: mkaasees
  chat server full report project report tiger 10 16,578 06-11-2015, 07:20 PM
Last Post: Guest
  e-banking project and implimentation seminar presentation 10 18,621 08-07-2015, 04:29 PM
Last Post: Guest
  email flyer design full report project report tiger 9 27,937 26-02-2015, 03:06 PM
Last Post: oiajecuot
Rainbow [b]Get abstracts/ synopsis of latest IEEE project and implimentations for Free!!![/b] Shital3144 63 11,059 08-12-2014, 02:01 AM
Last Post: buy viagra online
Brick V3 MAIL SERVER full report project report tiger 4 6,508 04-10-2014, 02:39 PM
Last Post: GaCcBuH
  data mining full report project report tiger 35 199,299 03-10-2014, 04:30 AM
Last Post: kwfEXGu
  Project Report On OnLine Cab Service project girl 1 976 22-08-2014, 07:29 PM
Last Post: HKGSuIeNq