What Are Requirements?
System non system( System, non system ) Requirements: analyse Functional parting( analyse, Functional, parting ) requirements Non-functional analyse parting( Non-functional, analyse, parting ) requirements
FURPS+ Requirements Acronym?
requirements requirements requirements requirements requirements + even more categories…
Information Gathering Techniques Choose 6 that apply.
Interviewing users and other stakeholders
Distributing and collecting questionnaires
Reviewing inputs, outputs, and documentation
Observing and documenting business procedures
Researching vendor solutions
Collecting active user comments and suggestions
Making a speech in public
System Diagnosis
choose 6 that apply Reasons for Modeling
Communicating with a variety of users and stakeholders
Documenting what was done for future maintenance/enhancement
Learning from the modeling process
Reducing complexity by abstraction
Remembering all the details
Communicating with other development team members
Using Data to help team
Applying customer skills
Some Analysis and Design Models Choose 8
Event List
Use Case Diagram
Use Case Description
Location Diagram
Class Diagram
Sequence Diagram
Communication Diagram
State Machine Diagram
Venn Diagram
Database Diagram
Documenting Workflows with Activity Diagrams
Workflow.
describes user (or system) activities, the person who does each activity, and the sequential flow of these activities Useful for showing a graphical model of a workflow A UML diagram
sequence of processing steps that completely handles one business transaction or customer request
Activity Diagram
Use Cases — an activity that the system , usually in response to a by a user Use cases define functional requirements Analysts decompose the system into a set of use cases (functional decomposition) Two techniques for Identifying use cases User goal technique Event decomposition technique Name each use case using Verb-Noun
Use Case Diagrams
Use case diagram— a model used to graphically show uses cases and their relationships to actors Recall UML is , the standard for diagrams and terminology for developing information systems Actor is the UML name for a end user Automation boundary— the boundary between the computerized portion of the application and the users who operate the application
Use Cases and CRUD CRUD technique – A good cross-check against the existing set of use cases. Used in database context Ensure that all classes have a complete “cover” of use cases Not for primary identification of use cases
Three Layer Architecture
Stakeholders of a comprehensive accounting system for public company
Verifying use cases for Customer
DA and DBA Responsibilities
First Normal Form
A ❌ is in first ❌ form if ❌ field ❌ only one value. Not ❌ ❌ in an ❌ Not ❌ number of ❌
Second Normal Form A table is in Second Normal Form if it is First ❌ Form and each ❌ ❌ is only ❌ ❌ on the entire primary key. This ❌ only arises with tables that have ❌ ❌
Third Normal Form A table is in Third Normal Form if it is in ❌ and NO ❌ (or set) is ❌ on any other non-key attribute (❌) In other words, no ❌ among any ❌
Steps of Object-Oriented Design Three paths Simple use case use CRC Cards Medium use case use Communication Diagram Complex use case use Sequence Diagram
Example of CRC Card
Example of System Requirment
Activity Diagrams Symbols
Name Analyse and design models
Metaphors of Human Computer Interaction
Many to Many Relationship
User Case Diagram
Systems Analysis Activity
Bitte warte - es wird geladen…