Shaped Model Activities

The V-shaped model, described in Chapter 4 and shown in Figure 4-10, is a linear arrangement of most of the activities inTable 9-1. similar to the waterfall model. The checklist for the V-shaped model's tasks and activities is shown in Table 9-4.

Table 9-4. V-Shaped Model Checklist of Potential Activities and Tasks

Life Cycle Phase

Potential Activities

Potential Tasks

Project and requirements planning— Determining the system requirements and how the resources of the organization will be allocated to meet them

® Initiate the project

• Map activities to the SLCM ® Allocate project resources ® Establish project environment ® Plan project management

® Explore the concept

® Identify ideas or needs ® Formulate potential approaches ® Conduct feasibility studies ® Plan system transition (if applicable) ® Refine and finalize the idea or need

® Manage software quality

® Plan software quality management ® Define metrics

Product requirements and specification analysis—Analysis and specification of the expected external behavior of the software system to be built

® Analyze system allocation

® Analyze functions ® Develop system architecture ® Decompose system requirements

® Identify software requirements

® Define and develop software requirements ® Define interface requirements ® Prioritize and integrate software requirements

Architecture or high-level design— Defining how the software functions are to implement the design

® Perform high-level design ® Perform architectural design

Life Cycle Phase

Potential Activities

Potential Tasks

® Design the database (if applicable) ® Design interfaces

Detailed design— Defining and documenting algorithms for each component that was defined during the architecture phase

® Select or develop algorithms (if applicable) ® Perform detailed design

Coding— Transforming the algorithms defined during the detailed design phase into software

® Create source code ® Generate object code ® Create operating documentation

Unit testing— Checking each coded module for errors

® Plan testing ® Develop test requirements ® Create test data ® Execute the tests

Integration and testing— Interconnecting the sets of previously unit-tested modules to ensure that the sets behave as well as the independently tested modules did during the unit testing phase

® Plan integration

• Perform integration

® Develop test requirements

• Create test data

• Execute the tests

System testing— Checking whether the entire software system (fully integrated) embedded in its actual hardware environment behaves according to the software requirements specification

® Plan testing ® Develop test requirements

Life Cycle Phase

Potential Activities

Potential Tasks

® Create test data ® Execute the tests

Acceptance testing— Allowing the users to test the functionality of the system against the original requirements. After final testing, the software and its surrounding hardware become operational. Maintenance of the system follows.

• Plan installation

• Distribute software

• Install software

• Develop test requirements

• Create test data

• Execute the tests

• Accept software in operational environment

Production, operation, and maintenance— Putting software into production and providing for enhancement and corrections

® Operate the system

® Provide technical assistance and consulting ® Maintain support request log

Inteqral activities— See Table 9-2.

Project Management Made Easy

Project Management Made Easy

What you need to know about… Project Management Made Easy! Project management consists of more than just a large building project and can encompass small projects as well. No matter what the size of your project, you need to have some sort of project management. How you manage your project has everything to do with its outcome.

Get My Free Ebook

Post a comment