The Requirements Document Development

Published Date: 02 Nov 2017

Project management ( Margaret Rouse,Project Management,2008 )is a methodical approach to planning and guiding project processes from start to finish. According to the Project Management Institute, the processes are guided through five stages: initiation, planning, executing, controlling, and closing. Project management can be applied to almost any type of project and is widely used to control the complex processes of software development projects.

Here is the main feature of Project Management:

Project management is no small task.

Project management has a definite beginning and end. It is not a continuous process.

Project management uses various tools to measure accomplishments and track project tasks. These include Work Breakdown Structures, Gantt charts and PERT charts.

Projects frequently need resources on an ad-hoc basis as opposed to organizations that have only dedicated full-time positions.

Project management reduces risk and increases the chance of success.

Project management (Duncan Haughey,Introduction to Project Management,2011)is often summarised in a triangle (see Figure 1). The three most important factors are time, cost and scope, commonly called the triple constraint. These form the vertices with quality as a central theme.

F1

.Projects must be within cost.

.Projects must be delivered on time.

.Projects must be within scope.

.Projects must meet customer quality requirements.

More recently, this has given way to a project management diamond, with cost, time, scope and quality the four vertices and customer expectations as a central theme (see Figure 2). No two customer expectations are the same so you must ask what their expectations are.

F2

Overview of the Project

As new technology development faster and faster,the enterprises are require to using all kinds of information and technology to produce many different product for different customer.

Our company is a Wafer Manufacturer,we have a lot of customers and they often have different requirement for their new product,so we must catch up with these customers’ requirement and we can get orders, and the company can become more and more compete.Here is an example of our company research and development a new product.

Major Milestones:

Milestone

Milestone description

Dependency

Resources

Due Date

1

Requirements Analysis

0

A

14/01/13

2

Verification

1

B

21/01/13

3

Validation

1

C

21/01/13

4

Requirements Solution Statement

1

A,B

17/01/13

5

Requirements Refinement

2

C

24/01/13

6

Solution Analysis

3

A

23/01/13

7

Product Specification & Design

4，5

C

04/02/13

8

Product Implementation

7

D

25/02/13

9

Product Testing

8

C

07/03/13

In regard to application development, the major milestones are broadly defined. The above table lists the milestones in relative chronological order along with their dependent tasks, the number of people working on them, and the date they are due.

Gantt Chart:

The schedule as outlined below only defines the first tasks we are to complete. This is simply because we don't know enough information about the later tasks at this early stage. As more information comes to hand, this will be updated accordingly.

Not that the verification and validation tasks here only indicate the processes in regard to the functional prototype, not the final system

In the above chart, the red and blue bars indicate the planned start, duration and end dates while the dashed bar represents the "slack" time in which we can finish the task without adversely affecting the time specified for later tasks. From this chart we can have an general idea that we have 48 days to finish this project.

As we know in the actually operation we can not make every step and every staff perform 100% efficiency.In the chart there also have ‘total slick’,that is mean we can improve efficiency base on the ‘total slick’.so we can insert one task call’buffer’ time and we will get one new chart .(see below):

In the above chart the yellow bar indicated ‘buffer time’that we can improve,of course this is not actually period.After insert buffer time we get a new chart and more efficiency project.The period of this project become 45 days .

Procedures

3.1 Requirements Analysis

In order to build the correct product we need to analysis the given requirements in detail. The requirements statement given to us only gives us a broad idea regarding what functionality the system needs to provide. From this we need to flush out what is needed and what is not .

In order to do this effectively we have chosen to implement a functional prototype. This will enable us to show the client our exact interpretation of the requirements. The client can then say, "No that's not what I meant," "Yes that's it" or better yet, "Yes but I want it to look like this."

During the process of building the prototype we will not only be determining what our interpretations of the requirements are, but also learning about the technologies required to implement them and more concretely establishing our development and quality assurance processes.

3.2 Verification

Verification is basically the process of determining whether we are building the right product. Once the prototype is complete we will spend some time in consultation with our client performing requirements verification. This will involve an iterative two step process:

1 Determine what's missing or not required

2 If updates still required

2.1 Update the prototype 2.1.1 Return to step 1

2.2 Otherwise stop verification

It should be noted that verification is an ongoing process. At the each completion of each milestone, we will need to perform a verification analysis to make sure we are still on track. Similar to the above process, this will be in conjunction with the client.

Following the completion of this verification phase, we will be ready to begin defining the system we intend to build more precisely. This will be in the form of the Requirements Solution Statement.

3.3 Requirements Document Development

The requirements solution statement is an abstract definition of the functional and non-functional requirements of the system as we have interpreted them. It will be targeted at both the application engineers and the client and as such will be in a form readable and understandable by both. It will serve as the contract between ourselves and the client by defining exactly what we have to provide. The requirements document also serves as a basis for QA to develop testing procedures for the development/testing phase of the project.

As stated above, verification will once again take place. We will present the solution statement to the client and perform a requirements review. This will involve working through each functional and non-functional requirement, explaining the implications of each to the client. Any omissions, errors, conflicts or contradictions need to be formally recorded and resolved.

3.4 Validation

Validation is the process of making sure we are building the product correctly. That is, making sure it is not faulty or "buggy." Throughout development, weekly builds of the software will be declared and handed to the Quality Assurance (QA) team.

QA will then perform various testing procedures on the product and present the defects to the application engineers to fix. Once all the defects found by QA have been fixed, another build is declared and the process repeats itself.

The actual testing process is defined more precisely in the testing section later in this document.

3.5 Solution Analysis

Once we have our final solution statement, we need to design the final product. Given that we have already built the functional prototype by this stage, we should have a good idea as to how to go about building the system.

We will be able to look at the design of the prototype and determine:

.what worked well

.what needs to be redesigned

.what needs to be thrown away altogether

.what needs to be added.

This will form the basis of the Product specification and design.

3.6 Product Specification and Design

This will be based on the solution statement and our solution analysis. It will include implementation specific information such as class diagrams, object models and so forth. At this stage the specification and design process is relatively undefined, as the project develops more information will become available.

3.7 Product Implementation

As above, the process of implementation will become clearer as it comes closer and will be defined at a more appropriate time.

3.8 Testing

The purpose of this Verification and Validation Plan for the Team Synergy Product, is to document the planned steps taken by Synergy to ensure that the product developed is of high quality in relation to what the customer has requested. In other words, it assures that we take steps so that:

.We build the right product.

.We build the product right.

A brief introduction that explains the content of the following three sub-sections, which are:

.Functional aspects that need to be tested

.Non-Functional aspects that need to be tested

.Test sections and example tests

Project Management use in our company

4.1Project Scope Management

Project scope management is the process that ensures all the factors and variables for defining and controlling the project are included. This includes project planning and cost control, trade off analysis, project charter preparation, the kickoff meeting, a scope-of-work statement, validation of the project scope, and initiation of a change control process.

In our company we want our customer are satisfied with our product .As many different requires we should expansion our scope to produce more and more new product .

4.2Project Time Management

Project time management ensures completing a project on time,which is one of the major challenges for any project manager. It includes activity definition and sequencing, duration estimation, schedule development, and schedule control. Bar charts, the CPM/PERT technique, resource allocation and leveling, network crashing, and fast tracking of projects are used to effectively manage the project schedule.

There are no standard templates for project schedules. The process of schedule development is unrealistic and out of sequence. We use Microsoft Project2010 to plan our schedule ,and with the Gantt Chart we can improve our schedule and make our team become more efficiency.

4.3Project Cost Management

Project cost management ensures that the project is completed within the approved budget. Cost management is crucial because cost overruns are common resulting in serious cost problems during project execution. Project cost management includes resource planning, cost estimating, cost budgeting and control, earned value analysis, and depreciation and capital budgeting.

We have formal cost estimating tools and techniques that are optimized and sustained for continuous PM process improvement.

4.4 Project Human Resource Management

Project human resource management ensures the most effective use of the people involved with the project. It is to manage, motivate, and organize people effectively. It includes assigning project roles and responsibilities, reporting organizational relationship, staffing, motivation, leadership, team development, and conflict resolution.

We can improvements in both individual skills and team capabilities are integrated to perform effectively. Organization is rewarded and recognized by project-oriented teams.

4.5 Project Risk Management

Project risk management identifies, analyzes, and responds to project risk. It includes defining, identifying, and quantifying risk; formulating risk mitigation strategies; and developing appropriate risk response and control processes.

our organization uses lessons learned information for risk identification, response, and control. Potential risk sources are prepared and reviewed for use of other PM knowledge areas.

4.6 Project Quality Management

Project quality management ensures that the project will meet or exceed all activities of the overall management function. It includes an overview of quality concepts, the cost of quality, statistical process control, variation and measurement, and quality improvement.

Acknowledge of PM

With the PM model, an organization evolves from a less PM sophisticated organization to a highly project-oriented organization. This does not mean that an organization at level N+1 always uses level N characteristics on a project. Rather, at level N+1 an organization has a capability to selectively choose the proper and eligible PM practices or tools that are suitable for a given project.

As an example, assume that scheduling techniques evolve from drawing simple bar charts, to developing project network diagrams, to conducting a complex simulation for resource optimization. An organization that has a high PM level does not always have to conduct expensive simulation or resource leveling techniques to find an optimal schedule or resources using highly sophisticated PM tools. At a higher PM level, an organization can use its discretion to apply the best set of PM processes and requirements based on the nature or complexity of a project.

Conclusion

It is well suited to assess an organizational PM level. Furthermore, the PM model provides an orderly and disciplined process to achieve higher levels of PM maturity. The PM model should be continuously refined to reflect advances in our PM knowledge base. This PM model could further determine and evaluate an organizational PM maturity level more effectively.

Also, the PM model should be applied to other industries and companies to further our understanding of PM in the future. By collecting and sharing this information, all PM organizations can benefit and continuously improve their PM practices. This information would be very helpful to managers who are struggling to calculate a budget to improve an organization’s overall PM practices.

Future research will continue to focus on understanding the PM maturity and its benefits of PM knowledge areas and processes more thoroughly. Real-world case studies reporting on how an organization has actually applied the PM model would also be beneficial to the PM community.