• Exercise 03 will open after the lecture, it is due as usual, the day before our next lecture (UML Class Diagrams) • First Midterm Exam Week 7 (September 29 / October 1) • Second Midterm Exam could be Week 12 (November 3 / November 5)
Requirement a) May state what (reactions, behaviours, or services) the system should not do. b) services the system should provide, c) how the system should react to particular inputs, and d) how the system should behave in particular situations.
• Search option given to user to search from various invoices. • User should be able to mail any report to management. • Users can be divided into groups and groups can be given separate rights. What about • A video game? • Canvas? • MyASU? • Facebook App?
Requirement Non-functional requirements a) Constraints on the services or functions offered by the system, such as Standards to apply, development platform, timing constraints, constraints on the development process, etc. b) Quality attributes, such as performance specifications, robustness, usability, etc.
(Quality) Property Measure Speed • Processed transactions/second • User/event response time • Screen refresh time Size • Mbytes • Number of ROM chips Ease of use • Training time • Number of help frames Reliability • Mean time to failure • Probability of unavailability • Rate of failure occurrence • Availability Robustness • Time to restart after failure • Percentage of events causing failure • Probability of data corruption on failure Portability • Percentage of target dependent statements • Number of target systems
(Constraints) • Should comply FERPA regulations. • Software is developed keeping downward compatibility intact. What about • Pac-man? • Canvas? • MyASU?
Yourselves 1. The system must be able to capture federal and state tax table information. 2. The system must provide the ability to merge two accounts/records where one account is for the same person with an incorrect social security number by allowing the user to click the incorrect, make the changes to the correct account, and then delete the incorrect account automatically after an account has been locked for this purpose 3. Right after the game gets started, a dialog will show up to prompt the player enter his/her name. 4. The player rolls a dice by clicking on a button labeled “role dice”. A dialog pops-up to indicate the value of the dice roll. In this game, there are two six-faced dice.
Yourselves 1. The system must be able to capture federal and state tax table information. 2. The system must provide the ability to merge two accounts/records where one account is for the same person with an incorrect social security number by allowing the user to click the incorrect, make the changes to the correct account, and then delete the incorrect account automatically after an account has been locked for this purpose 3. Right after the game gets started, a dialog will show up to prompt the player enter his/her name. 4. The player rolls a dice by clicking on a button labeled “role dice”. A dialog pops-up to indicate the value of the dice roll. In this game, there are two six-faced dice. F F F F
Yourselves 5. The system shall allow a user to interface with it through mouse events on buttons and drop down boxes and keyboard events on text fields. 6. All code development shall be done with the Java programming language. 7. Modified data in a database should be updated for all users accessing it within 2 seconds 8. The system shall be accessible to people with disabilities in accordance with the Americans with Disabilities Act of 1990.
Yourselves 5. The system shall allow a user to interface with it through mouse events on buttons and drop down boxes and keyboard events on text fields. 6. All code development shall be done with the Java programming language. 7. Modified data in a database should be updated for all users accessing it within 2 seconds 8. The system shall be accessible to people with disabilities in accordance with the Americans with Disabilities Act of 1990. NF NF NF NF
Yourselves 7. All monetary amounts must be accurate to two decimal places (integrity). 8. The new product shall be easy to use by adult members (age 18 to 80) of the public who may only have one hand free. 9. No piece of text that might be displayed to a user shall reside in program source code. Every piece of text that a user might see must be modifiable without changing source code. That is, no user-visible text will be “hard-coded.” 10.The payment subsystem design is based on the payment module from the ALPHA product line. The PAGO system should not be modified unless absolutely necessary.
Yourselves 7. All monetary amounts must be accurate to two decimal places (integrity). 8. The new product shall be easy to use by adult members (age 18 to 80) of the public who may only have one hand free. 9. No piece of text that might be displayed to a user shall reside in program source code. Every piece of text that a user might see must be modifiable without changing source code. That is, no user-visible text will be “hard-coded.” 10.The payment subsystem design is based on the payment module from the ALPHA product line. The PAGO system should not be modified unless absolutely necessary. NF NF NF NF
javiergs
tsoshiro
gam0022
otakakot
fukubaka0825
kazupon
mizoguchicoji
kyoheig3
ssssota
nashiusagi
junk0612
mot_techtalk
watanave
bermonpainter
tammyeverts
yeseniaperezcruz
rocio
bluesmoon
eileencodes
soudai
danielanewman
quramy
denniskardys
bcantrill
trishagee
![CSE360 – Introduction to Software Engineering Javier Gonzalez-Sanchez [email protected] Fall](https://files.speakerdeck.com/presentations/fec1ba31b2d244139cbd6d9f8dc3575a/slide_26.jpg){kind=link}