DOC PREVIEW
Toronto CSC 340 - Requirements Analysis

This preview shows page 1-2 out of 6 pages.

Save
View full document
View full document
Premium Document
Do you want full access? Go Premium and unlock all 6 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 6 pages.
Access to all documents
Download any document
Ad free experience
Premium Document
Do you want full access? Go Premium and unlock all 6 pages.
Access to all documents
Download any document
Ad free experience

Unformatted text preview:

Page ‹#›Information Systems Analysis and Design csc3402004 John MylopoulosRequirements Analysis -- 1VIII. Requirements AnalysisFunctional and Non-Functional RequirementsFunctional and Non-Functional RequirementsStakeholders Stakeholders From Whom Do We Gather Requirements?From Whom Do We Gather Requirements?How Do We Specify Them?How Do We Specify Them?Information Systems Analysis and Design csc3402004 John MylopoulosRequirements Analysis -- 2What Are Requirements?What Are Requirements?"...Requirements definition is a careful assessment ofthe needs that a system is to fulfill...must say whywhy asystem is needed, based on current and foreseenconditions, which may be internal operations or anexternal market...must say whatwhat system featureswill serve and satisfy this context...must also sayhowhow the system is to be constructed...”[Ross77] Requirements constitute a specification for the newsystem. They serve as a “contract” betweencustomers and developers.Page ‹#›Information Systems Analysis and Design csc3402004 John MylopoulosRequirements Analysis -- 3Requirements describeRequirements describethe systemthe systemwith respect to itswith respect to itsenvironment,environment,NOT its inner workings!NOT its inner workings!Information Systems Analysis and Design csc3402004 John MylopoulosRequirements Analysis -- 4Functional RequirementsFunctional Requirements Describe the processing (i.e., functions to besupported) by the new system. Describe the inputs into the system. Also describe the outputs of the system. Finally, they describe the data that must bemanaged by the system.Page ‹#›Information Systems Analysis and Design csc3402004 John MylopoulosRequirements Analysis -- 5Non-Functional RequirementsNon-Functional Requirements Describe how well the system supports thefunctional requirements (hence the name non-functional, or quality requirements). This description may include:Performance criteria;Reliability requirements;Security considerations;Usability requirements,…more...Information Systems Analysis and Design csc3402004 John MylopoulosRequirements Analysis -- 6Are Requirements Always Done inAre Requirements Always Done inSoftware Engineering Practice?Software Engineering Practice?Page ‹#›Information Systems Analysis and Design csc3402004 John MylopoulosRequirements Analysis -- 7Whom Do We GatherRequirements From?From the stakeholders stakeholders ((actorsactors)):Users - who are concerned about the featuresand the functionality of the new system;Designers;Systems analysts;Training and user support staff;Business analysts;Technical authors;The project manager;…more…Information Systems Analysis and Design csc3402004 John MylopoulosRequirements Analysis -- 8Stakeholders are Different forStakeholders are Different forDifferent Types of ProjectsDifferent Types of ProjectsCustomer-drivenCustomer-driven projects develop customized, one-ofsolutions.Market-drivenMarket-driven ones develop (generic) software that issold in the market. (Coming soon) User-drivenUser-driven projects develop softwarethat is downloaded and used -- for a fee, on demand. The concept of software is evolving from that of acustom-builtcustom-built artifactartifact, to that of a commoditycommodity that youbuy, and soon to that of a service/resourceservice/resource that youuse on demand.Page ‹#›Information Systems Analysis and Design csc3402004 John MylopoulosRequirements Analysis -- 9What Do We Gather?Scenarios (use cases) from which we can inferfunctional and non-functional requirements. Scenarios describe desirable sequences of eventsthat should be supported by the new system. They also describe undesirable ones that should beprevented.Information Systems Analysis and Design csc3402004 John MylopoulosRequirements Analysis -- 10How Do We SpecifyRequirements? Through (visual) modelingBut Remember:A Model is Usually just an Approximation!TheWorldSharedpropertiesProperties thatonly hold in themodelProperties thatonly hold in theworldTheModelDesignationsPage ‹#›Information Systems Analysis and Design csc3402004 John MylopoulosRequirements Analysis -- 11Additional ReadingsAdditional Readings [Kotonya98] Kotonya, G. et all. Requirements Engineering:Processes and Techniques, John Wiley & Sons, 1998. [Macaulay96] Macaulay, L., Requirements Engineering,Springer-Verlag,


View Full Document

Toronto CSC 340 - Requirements Analysis

Documents in this Course
Scoping

Scoping

10 pages

Load more
Download Requirements Analysis
Our administrator received your request to download this document. We will send you the file to your email shortly.
Loading Unlocking...
Login

Join to view Requirements Analysis and access 3M+ class-specific study document.

or
We will never post anything without your permission.
Don't have an account?
Sign Up

Join to view Requirements Analysis 2 2 and access 3M+ class-specific study document.

or

By creating an account you agree to our Privacy Policy and Terms Of Use

Already a member?