Itt1 sd requirements
Upcoming SlideShare
Loading in...5
×
 

Itt1 sd requirements

on

  • 366 views

Stakeholders and requirements.

Stakeholders and requirements.

Statistics

Views

Total Views
366
Views on SlideShare
366
Embed Views
0

Actions

Likes
0
Downloads
5
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as OpenOffice

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Itt1 sd requirements Itt1 sd requirements Presentation Transcript

  • Requirements System design 2010 Autumn Morten Bo Nielsen Mon@eal.dk
  • Project background● Vital questions ● Project owner ● Costumer ● User● More on this later in the course Is this a good metaphor for project backgrounds?System design - Mon@eal.dk 2
  • Analysis phase SDLC phases ● Analysis phase Planning ● What to built? Analysis ● What should it do? Design ● What should it not do? Implementation ● Does this relate to “problem statements”?System design - Mon@eal.dk 3
  • Requirements ● Project is done when requirements are fulfilled. ● Functional requirements ● What should the system be able to do? ● Non-functional requirements ● Extra stuff: Performance, company imposed constraints and other stuff. ● Be prepared for the question ”Why is that a requirement?” ● Check background...System design - Mon@eal.dk 4
  • Requirements - functional ● Process requirements ● What should the system do? ● Data/information requirements ● What should the system contain This is the requirements which define what the system should do.System design - Mon@eal.dk 5
  • Requirements – non-functional ● Operational ● Environment for proper operation. ● E.g. No direct sunlight. ● Performance ● Specific values of how well the system functions ● Security ● Cultural and political ● E.g. Must be CE certified.System design - Mon@eal.dk 6
  • Gathering requirements ● How to identify the Now improvement/features As-is system ● Think long enough? ● Ask someone? Improvement ● Who decides the requirements? Future To-be systemSystem design - Mon@eal.dk 7
  • Example ● Mashing example (again)System design - Mon@eal.dk 8
  • ExerciseYou are to built a remotecontrolled car. ● Decide on project owner, costumer and user ● Optional: Do a block diagram ● Discuss and decide on 10 requirements.System design - Mon@eal.dk 9
  • Top-down or bottom-up ● Both ways work ● Result differ ● Mileage differ ● Recall the “technician vs. engineer” difference.System design - Mon@eal.dk 10