Methodology and Work Plan

Version 1.0

Project ID

< F10201024>
<

Supervisor Name Pervez >

Muhammad Tariq

Revision History
Date Version Description (dd/mm/yyyy) 08/08/2011 1.0 MC080406542 MC090203207 Author Muhammad Attique Naseer Ahmad Mughal

Table of contents
Revision History 1. Introduction of the Planning Phase 2. Methodologies 2.1 Existing Methodologies 2.2 Adopted Methodology 2.3 Reasons for choosing the Methodology 3. Work Plan (Use MS Project to create Schedule/Work Plan)

1. Introduction of the Planning Phase

The system we are going to develop as our final project is an ELearning Tool for Minimizing Communication Gap and Interaction Delay (ELT-MCGID). This Planning document is developed to set the rules and procedures for the project.

1.1 Project Scope:

ELT-MCGID will minimize the communication gap between the students and teacher (Faculty Members) of Virtual University of Pakistan. It will also minimize the interaction gap which is definitely not as face to face but closer to face to face interaction. It is the best source for students to discuss their problems with teacher. In this way massive information will be shared.

1.2 Tools and Technologies:

ELT-MCGID software requires selection of the technologies required for the implementation of the project. 1.2.1 Front-End Technology (ASP.Net) ASP.Net is very valuable tool, as it allows us to build dynamic, rich web sites and web applications. 1.2.2 Back-End Technology (SQL) We will use SQL Server as back end to access user id and password on login page. 1.3 Project Feasibility: 1.3.1 Technical Feasibility: The system which is to be developed is ELT-MCGID web application, ASP.net along with SQL Server will be used to develop it. The software required for doing this project is easily available. 1.3.2 Operational Feasibility: The software will be designed in this way that it will be easy to use. It will also provide additional help to operate the software. It will be simple and friendly users. 1.3.3 Economic Feasibility: There is no need for purchasing the tools and license used during the development of the project. All tool and technologies that are required during development are already with the development team. This makes the development economically feasible. Only

costing factor is the effort of the project members and time that is utilized in project development process. 1.3.4. Schedule Feasibility: Time is an important factor. We have got the required resources to complete the project on time. We all are in the final semester of our program and there is sufficient time available to us for completing this project on the required date and time. 1.3.5. Specification Feasibility: The project team has a clear picture of what we have to develop and what the system must have in it to be successful. The project team will have a complete and clearer picture when we are through with the requirements specification and gathering phase. The requirements are becoming clearer and definite with the passage of time.

1.4 Risk Analysis and Planning:

S. # 1 Risks Risk Type The schedule Schedule pressure can force Risk some function points to be changed or dropped from being implemented as planned in the planning phase. The requirements can Scope Risk change over time. Probabili Mitigation Actions ty 50% We have divided the whole process in modules. All Activities are listed with proper planning, and sufficient time allocated to each activity. 40% Sufficient time is provided for requirement elicitation. The applicable changes will be handled if possible. 30% The product will be built by using relatively independent modules so that any new functionality can be added. 25% A relatively simple and efficient solution will be

The product scope Scope Risk can keep expanding.

The transaction time Technologi can be a bit higher cal Risk

5.

7.

depending upon the internet speed This is a simple People Risk project so it can result in some pressures and problems because of the lack of experience. The users of the Technologi system might need cal Risk some time to get familiarize with the system

found and tried. 15% Supervisor of Project will be consulted. Lack of experience will be reduced by the usage of knowledge and technology. The user will be provided with sufficient on the hands help to learn the usage of the system early and easily.

10%

2. Methodologies
2.1 Existing Methodologies
2.1.1. Waterfall Model. Waterfall method is a documentation-driven model. Because of the cascade from one phase to another this model is known as Waterfall model. It is also known as a linear sequential model. In water fall model software is developed in following stages. 1. Requirement Analysis and Definition The system services, constraints and goals are established by the consultation with system users. Then defined in detail and serve as a system specifications System and software design It establish system overall architecture. This phase describes desired features and operations in detail. Implementation and unit Testing In this stage software design is realized as a set of programs and each unit is verify against its specifications. Integration and System testing This stage brings all the individual system components into one, then testing it for errors, bugs, etc. After testing software is delivered to customer Installation and Deployment It is the final stage of development in which software is put into production

2. 3. 4.

5.

6.

Maintenance In this stage errors are corrected which are not discovered in earlier stages of the life cycle.

2.1.2. Build and Fix Model. Product is constructed without specifications. Product is built and then modified until the client is satisfied. This model may work for small project.

2.1.3. Rapid Prototyping Model.

This model we used to overcome issues related to understanding of user requirements. Emphasis is on creating a prototype that looks and acts like the desired product in order to test its usefulness. Develop a system with reduced capability. Present to client for approval. Once the prototype is approved, it is discarded and the real software is developed.

2.1.4. Incremental Model In Incremental Model the Product is partitioned into smaller pieces which are created and tested separately. Each build contains an operational quality subsystem. Each Additional build is integrated with the previous build. As each build is much smaller as compare to product therefore it can be sent to the client quickly. A quick feedback from the client can be taken and requirement related error can be incorporated at a much lesser cost. 2.1.5. Synchronize and stabilize Model. It is Type of Incremental Model. First Requirements are captured, Specifications are drawn up. Project is divided into 3 or 4 builds. Each build carried out by small teams which work in parallel At end of each day the code is synchronized (test and debug).

At the end of the build it is stabilized by freezing the build and removing any defects. 2.1.6. Spiral Model. Spiral Model was developed by Barry Boehm The Spiral Model is the Waterfall Model plus risk Analysis. Risk management approach is employed to software development in the stages of Specification, Design, Implementation and Integration. Each stage is preceded by identification of alternatives and risk analysis and is then followed by evaluation and planning for the next phase. If risk can not be resolved the project is terminated immediately. Emphasizes the need to reiterate earlier stages a number of time as the project progresses. If one prototype is finished, a developer can proceed to the next prototype. Build, test and integrate to the first prototype. Helps demonstrate a proof of concept early in the cycle. Incorporates prototyping and software quality objectives

2.1.7. Fountain Model. Fountain model is object-oriented lifecycle model. It Support Incremental Development. In Fountain model all the activities are overlap to each other throughout the development cycle. Parallelism among various phases and iteration within phases

2.2 Adopted Methodology

Adopted Methodology for our project ELT-MCGID is E-Learning Tool for Minimizing Communication Gap and Interaction Delay, which is a combination of Waterfall and Spiral Model. Waterfall Model which is a sequential model in which development process of software goes through a number of phases in a certain order and Spiral Model which involves iterations of stages in which Associated Risk with the Project are identified and Analyzed with each stage. Using Waterfall Model our project will go through the stages of Requirement Analysis, System Design, Implementation and Unit testing, Integration and System Testing and Maintenance. Using Spiral Model Risk Management Approach will be used for each Stage.

2.3 Reasons for choosing the Methodology

Reasons for Choosing the Waterfall Model and Spiral Model are: Waterfall method is simple, easy to use. In Waterfall method software is developed into phases and each phase is precisely documented therefore it is easy to manage. Pre planning in waterfall method in each phase makes it more economical because it identifies any potential problems at the outset. Using Spiral Model Risk Analysis applied to each phase of software development and all possible risk associated with the project are identified and analyzed. Spiral Model adds more flexibility in project.

3. Work Plan (Use MS Project to create Schedule/Work Plan)

ID

T a sk N a m e

J u l2 0 1 1

A u g 011 2

S ep 011 2

O c2011 t

N o v 011 2

D ec 011 2

7/3 7/1 0 7/1 7 7/2 4 7/3 1 8/7 8/1 4 8/2 1 8/2 8 9/4 9/1 1 9/1 8 9/2 5 1 0 1 0 1 0/1 6 1 0/2 3 1 0/3 0 1 1/6 1 1/1 3 1 1/2 0 1 1/2 7 1 2/4 1 2/1 1 1 2/1 8 1 2/2 5 /2 /9

1 Req u ir em en t A n a lysis 2 P la n n in g P h a s e 3 A n a lysis a n d D esig n P h a se 4 D evelo p m en t 5 Fin a l P r o jec t