At a glance
Requirements Definition with UML
Designed for an audience that already has an understanding of analysis and requirements, and who wish to make use of the Unified Modelling Language (UML) to convey these requirements, feeding into systems design.
This course is designed to be delivered in-house, and will be tailored to fit the circumstances of the customer. Driven around a case study (ideally a current project), the course length can vary - but typically is from two to four days duration.
Intended For
As an in-house course, the full project team should be involved in this course, including - Business analysts, project managers, project leaders, developers, and designers.
Prerequisites
Participants are expected to have an understanding of analysis and requirement activities.
For less experienced team members, a suggested lead-in course is Software Education’s “Business Systems Analysis” course.
Participants are expected to have an understanding of analysis and requirement activities.
For less experienced team members, a suggested lead-in course is Software Education’s “Business Systems Analysis” course.
Learning Outcomes
By the end of this course, participants will be able to:
- Understand the correct use of Use Cases
- Produce Use Case descriptions
- Use Function Point Analysis to estimate Use Case size
- Produce and use a number of entity diagram techniques
Furthermore, it is intended that the current project ‘case study’ will have reached a point where all team members are comfortable with their roles and responsibilities and able to drive the project forward back in the workplace.
Content
- Introduction to object oriented concepts
- Overview of Unified Modelling Language
- Fundamentals of requirements definition
- Introduction to Use Cases
- Actors
- Use Cases
- Preparation of the Use Case List (also known as the Use Case Survey)
- Naming Use Cases
- Differentiating between Use Cases & Business Processes
- Differentiating between Use Case & User Interfaces
- Producing Use Case brief descriptions
- Use Case prioritisation
- Detailed Use Case descriptions
- Basic flow of events
- Alternative flows of events
- Pre-conditions
- Post conditions
- Special requirements
- "Other Stuff"
- Use Case diagrams
- The actor icon
- The Use Case icon
- Communicates associations
- Unidirectional communicates associates
- Bi-directional communicates associates
- Differentiating between Use Case diagrams & flow-charts
- Advanced Use Case concepts
- Use Cases Use of <<includes>> and <<extend>> relationships
- Concrete & abstract Use Cases
- Estimating Use Case size & effort using function points
- Overview of interaction diagrams
- Boundary, controller & entity objects
- Collaboration diagrams
- Sequence diagrams
- Producing collaboration diagrams
- Producing sequence diagrams
- Overview of class diagramming
- Association
- Inheritance
- Aggregation and composition
- Producing class diagrams from collaboration diagrams
- Course summary and review
Method Used
Tailoring the Course
The course participants and the client will gain maximum benefits from this course when it uses a current live client project. To enable this, the client must supply the instructor with a briefing and background material about the chosen project.
Sometimes the client wishes the instructor to include the use of CASE tools in the course; where this is the case, the client must supply the appropriate software and hardware within the course venue. The client must also supply, if necessary, the instructor with a properly licensed copy of the software at least ten working days prior to commencement of the course. The instructor will remove the software from his computer upon completion of the course.
