INFO 380 Lecture Notes - Lecture 6: Business Logic, Functional Requirement, Business Case
INFO 380 Lecture 6
Documenting Requirements
- Documentation
o Why:
▪ Give team members and stakeholders shared understanding of needs
▪ Write down things to clarify details
▪ Help identify what if scenarios
▪ Know when you are “done”
o Clear, effective communication → successful systems development
- Audience – people who need to know business objectives/high level picture/user’s
perspective/details
- Document journey
o High level to detailed + focused
o Business case shows project’s value → vision & scope to flesh out concept →
requirements document to provide details for building system
- Writing requirements
o Characteristics: avoid confusion, verifiable/testable, traceable/uniquely
identifiable
▪ Brief, clear, verifiable, traceable/uniquely identifiable
o Methods
▪ Functional requirements
• Features, business logic, user interfaces, web services,
authentication, transaction/data management, sort orders,
user/file management
• Inputs → behavior → outputs
• System Example: [optional precondition] [optional trigger event]
the system shall [expected system response]
o “if the student has an assignment who’s due date is today,
the system shall send an email to alert the student’s email
address
• User example: The [user class or actor name] shall be able to [do
something] [to some other object] [qualifying conditions,
response time, or quality statement]
Document Summary
Documentation: why, give team members and stakeholders shared understanding of needs, write down things to clarify details, help identify what if scenarios, k(cid:374)o(cid:449) (cid:449)he(cid:374) you are (cid:862)do(cid:374)e(cid:863, clear, effective communication successful systems development. Audience people (cid:449)ho (cid:374)eed to k(cid:374)o(cid:449) (cid:271)usi(cid:374)ess o(cid:271)je(cid:272)ti(cid:448)es/high le(cid:448)el pi(cid:272)ture/user"s perspective/details. Document journey: high level to detailed + focused, busi(cid:374)ess (cid:272)ase sho(cid:449)s proje(cid:272)t"s (cid:448)alue vision & scope to flesh out concept requirements document to provide details for building system. Writing requirements: characteristics: avoid confusion, verifiable/testable, traceable/uniquely identifiable, brief, clear, verifiable, traceable/uniquely identifiable, methods, functional requirements, features, business logic, user interfaces, web services, authentication, transaction/data management, sort orders, user/file management. Identifies use cases the system needs to support. Identifies what needs to happen when something goes wrong: actors someone/something that interacts with the system, people(users) / other systems or apps / devices, diagram use case, written use case, builds on use case diagram.
