characteristics of good requirements
DESCRIPTION
Term That FRefers To Requirement EngineeringTRANSCRIPT
M Saeed Arshad
Bachelor In Science Specialize In Software Engineering
Roll# 1656
Govt College University Faisalabad, Pakistan
Characteristics Of Good Requirements
04/13/2023 05:57 PM
Government College University Faisalabad, Pakistan
Requirement Are The Needs Of Customer That He Wants To Be Fulfilled By The Developer Team . It Actually Tells That What The Application(Product) Must Do.
Requirement
04/13/2023 05:57 PM
Government College University Faisalabad, Pakistan
Site Is About?
Which Type Of Stuff You Want To See On Your Site
Website Must Have Log-In Page
Examples
04/13/2023 05:57 PM
Government College University Faisalabad, Pakistan
Characteristics Of Good Requirements
04/13/2023 05:57 PM
Government College University Faisalabad, Pakistan
A Requirement is consistent if there is no requirement that conflict with it.
Different requirements may use different terms to refer the same object. There may be logical conflict between them.
Consistent
04/13/2023 05:57 PM
Government College University Faisalabad, Pakistan
• User Must Login To Download Something Otherwise Login Approvals Are Not Necessary.
• User Must Login To Do Any Kind Of Activity.
Example
04/13/2023 05:57 PM
Government College University Faisalabad, Pakistan
• Requirement should Explain Itself Completely.
• Should Have No Unambiguous Sense.
Clear
04/13/2023 05:57 PM
Government College University Faisalabad, Pakistan
Not Clear: System Should response quickly.
Clear: System Should response in 3 Seconds.
Example
04/13/2023 05:57 PM
Government College University Faisalabad, Pakistan
• A Good Requirement Is Easily Verifiable.
• A requirement is verifiable if and only if there exists some finite cost-effective process with which a person or machine can check Its Verification
Verifiable
04/13/2023 05:57 PM
Government College University Faisalabad, Pakistan
Non Verifiable: System Should Be User-Friendly
Verifiable: System Should Have Menu Bars, Dialog Boxes ,, etc
Example
04/13/2023 05:57 PM
Government College University Faisalabad, Pakistan
• The origin and author of Good requirement is Always clear.
• Each requirement is individually numbered.
• We Must Know Which Stakeholder Has Given This Requirement , As We Can Refer Him In Case Of Any Confusion.
Traceable
04/13/2023 05:57 PM
Government College University Faisalabad, Pakistan
• UL#1 For User Login.
• UR#2 For User Registration
Example
04/13/2023 05:57 PM
Government College University Faisalabad, Pakistan
• The Requirements Are Focused On “What” Not “How”. This Is The Basic Difference Between Requirements And Specifications.
• Allows Software Experts To Design Solutions Based On The Capabilities Of their Product That Are Supportable Over Time.
Design Independent
04/13/2023 05:57 PM
Government College University Faisalabad, Pakistan
The requirements are usually prioritized according to their importance to the solution, i.e.,• High (essential)• Medium (beneficial/desirable)• Low (optional)
Prioritized
04/13/2023 05:57 PM
Government College University Faisalabad, Pakistan
• System Should Have Login Page (High)
• System Should Display Data According To User Requirement(Medium)
• Stakeholder Can Comment(optional)
Example
04/13/2023 05:57 PM
Government College University Faisalabad, Pakistan
• The Requirements Are Written In A Way That Allows Them To Be Understood By All Stakeholders In The Project
Understandable by All
04/13/2023 05:57 PM
Government College University Faisalabad, Pakistan
• A Requirement Fd#7 Should Act As Mandatory For Login Approval.
• Here There Are Different Terms Than A Non Technical Person Can’t Understand..
Example
04/13/2023 05:57 PM
Government College University Faisalabad, Pakistan
• A Good Requirement Definitely Increase Performance Of System.
• Each Requirement Has It’s Own Importance In Working Of System.
Mandatory
04/13/2023 05:57 PM
Government College University Faisalabad, Pakistan
Importance
04/13/2023 05:57 PM
Government College University Faisalabad, Pakistan
• Good Qualities Give A straight Way To Solve Problem.
• We Can Satisfy The User If Requirements Are Clear By Developing The Exact The Product As He Wants.
• Can Manage The Product Well
• In Result Of Delivering Of Required Product, Our Demand Would Be Increased.
• Can Deliever The Product Well In Time And In Cost Limits.
Importance
04/13/2023 05:57 PM
Government College University Faisalabad, Pakistan
• We Can Have Hurdles In Developing ,Testing And Maintaining Process.
• Product Can Not Be Declared Well On Time.
• Suppose The Product Is Delivered On Time, But We Can Not Satisfy The Stakeholder.
continue
If We Do Not Follow This??
04/13/2023 05:57 PM
Government College University Faisalabad, Pakistan
• Time And Cost Resources May Go Beyond Our Expectations.
• In Result Of All That , Reputation Of Our Software House Is Decreased.
04/13/2023 05:57 PM
Government College University Faisalabad, Pakistan
• Good Requirements Are The Back Bone Of Successful System.
• A System Can Not Lead To Perfection With Out Good Requirement.
• Overall System Designing , Developing , Testing And Maintaining Directly Depends Upon Requirements.
Conclusion
04/13/2023 05:57 PM
Government College University Faisalabad, Pakistan
Thanks