SEO-Search Engine Optimization
Methodology and Work Plan
Version 1.0
Group Id:
Supervisor Name: Mr. Usman Waheed
Revision History
| Date (dd/mm/yyyy) | Version | Description | Author |
| 23/02/2012 | 1.0 | Methodology and work plan (Search Engine Optimization) | |
| | | | |
| | | | |
| | | | |
Table of contents
1. Introduction of the Planning Phase…...................................................................4
2. Methodologies……………………………………………………………………..5
2.1 Existing Methodologies……………………………………………………5
Spiral model…………………………………………………………...5
Incremental model…………………………………………………….6
Waterfall model……………………………………………………….6
Rapid application development model………………………………..7
Fountain model………………………………………………………..8
VU process model…………………………………………………….9
2.2 Adopted Methodology…………………………………………….9
2.3 Reasons for choosing the Methodology…………………………..9
3. Work Plan (Schedule/Work Plan)………………………………………………10
The Project Planning Phase is the second phase in the project life cycle. It involves creating of a set of plans to help guide the team through the execution and closure phases of the project.
The design, development, and implementation of an information system are a complex and expensive undertaking. Project planning is part of project management, which relates to the use of schedules such as Gantt charts to plan and subsequently report progress within the project environment.
Originally, the project scope is defined and the appropriate methods for completing the project are determined. Following this step, the durations for the various tasks necessary to complete the work are listed and grouped into a work breakdown structure. Then the necessary resources can be estimated and costs for each activity can be allocated to each resource, giving the total project cost. At this stage, the project plan may be optimized to achieve the appropriate balance between resource usage and project duration to comply with the project objectives. Once established and agreed, the plan becomes what is known as the baseline. Progress will be measured against the baseline throughout the life of the project
Advantages of planning phase:
· Business Requirements.
· Cost, Schedule, List of Deliverables and Delivery Dates.
· Resource Plan.
· Management Approval and proceed to next phases.
· A planning phase is any logical process used by a systems analyst to develop an information system, including requirements, validation, training, and user (stakeholder) ownership.
· Planning phase should result in a high quality system that meets or exceeds customer expectations, reaches completion within time and cost estimates, works effectively and efficiently in the current and planned Information Technology infrastructure, and is inexpensive to maintain and cost-effective to enhance.
A process is defined as a collection of related tasks with specific milestones. To ensure smooth progress of a software project, relevant processes are arranged and executed in a sequence. Every software project is discrete with respect to its complexity, size, and goals. Therefore, different process models are designed for different software projects. These process models provide approaches that decide the path of software development from the conceptualization of a project to its formal termination. Here are few of commonly used available methodologies.
Spiral model:
The spiral model combines the iterative nature of prototyping with the controlled and systematic aspects of the waterfall model, therein providing the potential for rapid development of incremental versions of the software. In this model the software is developed in a series of incremental releases with the early stages being either paper models or prototypes. Later iterations become increasingly more complete versions of the product.
Incremental model:
This model derives its name from the way in which the software is built. More specifically, the model is designed, implemented and tested as a series of incremental builds until the product is finished. A build consists of pieces of code from various modules that interact together to provide a specific function.
At each stage of the IM a new build is coded and then integrated into the structure, which is tested as a whole. Note that the product is only defined as finished when it satisfies all of its requirements.
This model combines the elements of the waterfall model with the iterative philosophy of prototyping. However, unlike prototyping the IM focuses on the delivery of an operational product at the end of each increment.
Waterfall model:
The waterfall model is a sequential software development process, in which progress is seen as flowing steadily downwards (like a waterfall) through the phases of Conception, Initiation, Analysis, Design (validation), Construction, Testing and maintenance. The waterfall development model has its origins in the manufacturing and construction industries; highly structured physical environments in which after-the-fact changes are prohibitively costly, if not impossible. Since no formal software development methodologies existed at the time, this hardware-oriented model was simply adapted for software development.
Rapid application development model:
Rapid Application Development (RAD) refers to a type of software development methodology that uses minimal planning in favor of rapid prototyping. The "planning" of software developed using RAD is interleaved with writing the software itself. The lack of extensive pre-planning generally allows software to be written much faster, and makes it easier to change requirements.
Fountain model:
The Fountain Model is a highly iterative approach that is well-suited to object- oriented software development. The Fountain Model allows for the fact that there is considerable overlap of activities throughout the development cycle— although some activities can't start before others.
Just as a fountain’s water rises up and falls back to the pool below, in object-oriented software development, the general workflow from analysis through design to implementation is overlaid with iterative cycles across many phases.
In this model the circles representing the various phases overlap, explicitly representing an overlap between activities. The arrows within a phase represent iteration within the phase. The maintenance cycle is smaller, to symbolize reduced maintenance effort when the object oriented paradigm is used.
VU process model:
VU Process Model which is a combination of waterfall and spiral models. In Vu process model you perform the same phases like requirements analysis and gathering, design, implementation, testing, as water fall model. This model also addresses risk factor in the project and tries to eliminate in development phase.
2.2 Adopted Methodology
We have adopted Process model. This methodology is the combination of strengths of other existing methodologies. As our requirements are well understood so we can say that this model is some how base on Waterfall model. This model is divided into five phases. It has the characteristics of spiral model as well. Our implementation includes the following stages/phases of “VU Process Model”.
· Gathering and Analyzing Requirements.
· Planning phase.
· Analysis and design phase
· Development phase.
· Final Report
Following reasons are there;
· Requirements are well understood and project scope is constrained.
· Sequence of Phases given in this methodology is well disciplined.
· It generates complete and comprehensive documentation and hence makes the maintenance task much easier.
· VU process model give us a template (from VU) that guides us in constructing a system.
· This model provides full description of every phase with helping material and tuitorials.
3. Work Plan (Use MS Project to create Schedule/Work Plan)
No comments:
Post a Comment