1 / 18

Requirement ( 必要条件 ) Specification( 规格 ) & Management process

Requirement ( 必要条件 ) Specification( 规格 ) & Management process. Requirement Management. Essential for successful project execution Improperly understood requirement leads to: Cost escalation( 增加 ) Late delivery( 递送 ) Poor quality Dissatisfied( 不满意的 ) Customers( 消费者 ).

beau-peterson
Download Presentation

Requirement ( 必要条件 ) Specification( 规格 ) & Management process

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Requirement (必要条件) Specification(规格) & Management process

  2. Requirement Management • Essential for successful project execution • Improperly understood requirement leads to: • Cost escalation(增加) • Late delivery(递送) • Poor quality • Dissatisfied(不满意的) Customers(消费者)

  3. Requirement Management process • The three major activity are • Requirement analysis(分析)& Specification • Requirement change(改变)management • Requirement traceability(可描绘)management • It satisfies the KPA of Level 2 change management • It satisfies the KPA of Level 3 “Software Product Engineering” process

  4. Requirement Specification:Objective • Specify all requirements(SRS) • Requirement Elicitation(引出)& Analysis • Requirement Documentation • Requirement review(回顾)

  5. Process for Requirement Analysis & Specification Prepare Gather/Elicit Requirement Analyze Obtain Sign-Off Review Prepare SRS & Acceptance Criteria

  6. Prepare • Prepare for requirement gathering & Analysis • Do background reading on technical/Business concepts & undergo training • Become familiar with customer methodology & tools to be used • Identify method for Information gathering • Prepare Questionnaires for eliciting information • Identify user group & Interviewees • Plan prototyping(原型) • Define requirement specification standards • Develop interview plan & review with customer

  7. Gather: • Gather Requirement • Establish Objective & scope of the system • Gather functional requirement • Business events, Input/output for each event, relationship between events • Gather information on external interfaces, operating environments, performance, standards & special requirements • Prepare prototypes & evaluate prototypes • Conduct feedback on understanding requirements

  8. Analyze: • Analyze requirements • Develop process model • Develop logical data model • Setup data dictionary • Then… • Prepare SRS document • Prepare acceptance criteria • Review & obtain signoff for SRS

  9. SRS Template • Overview(Introduction to the current system) • Current System (Brief Into to Current system) • Limitation of current system • Proposed system & Objective of proposed system • Functional Requirement (related to Customer business) • System requirement • Scope & Boundary • Context diagram • Business Events • External events (by user or client) / Temporal events (by time)

  10. SRS Template • Inputs/Outputs (for each Business Event) • Relationships (Between I/P & O/P) • Relationship Precedence • Screens & Reports • External Interface Requirements • The Application being developed may interact & pass compatible data with many other existing automated & nonautomated systems.

  11. SRS Template • Operating Environment Requirement • Hardware/software/network/communication • Performance Requirements • Response time, Transaction/sec, constraint on batch processing • Standards Requirements • User Interface, Detailed design, Coding, Document

  12. SRS Template • Special User Requirement • Security , Audit Trail, Reliability • Transaction Volume & data Volume • Backup & recovery • Legal • Data Migration, Data Retention • Installation, User Training, User Manual & help • Automated & Manual functions, Features not required • Constraint • Prototype • Glossary of Items

  13. Requirement Change management • Change is inevitable, This is Universal truth • Knowledge about what is possible makes desire better capability • Initially customer do not know fully what they want, as time passes they become clear what is desired • Prepare the project to handle these changes

  14. Requirement Change management • The process defines the set of activity performed when there are new requirement or changes in requirement. • Can occur at any time during project execution • The further down the lifecycle, the more severe the impact on the project. • Uncontrolled changes to requirement has adverse impact on cost, schedule & quality. • The requirement change management process ensure that a project succeeds despite requirement changes.

  15. RCM – The Process • Log the changes • Perform impact analysis(Risk Management) on the work products • Estimate efforts needed for the change request • Reestimate delivery schedule • Perform cumulative cost impact analysis • Review the impact with senior management, if thresholds are exceeded • Obtain Customer Signoff • Rework work Products.

  16. A Change request Example

  17. Traceability Management • The basic goal of a project is to build a software system that will satisfy the requirements • To aid this validation, traceability of requirement is important • Through tracing it can be validated that the software has met all requirements.

  18. Goals: • To check if all software requirement are satisfied. • There are two types • Forward Traceability • Backward Traceability • At Infosys The Traceability Matrix is used.

More Related