Presentation on theme: "IS21IS21 IS21 Lecture 13 – 2003/2004 1 System Scope from Business Use Case The scope of a system can be drawn around those business use cases which are."— Presentation transcript:
IS21IS21 IS21 Lecture 13 – 2003/2004 1 System Scope from Business Use Case The scope of a system can be drawn around those business use cases which are affected by a proposed new system. At this level it shows that some Business Processes (Use Cases) will NOT be affected by the new system - they are outside the scope. It also shows which External Business Actors will be affected by the new system. - They will need to be consulted and involved. - Their requirements will need to be understood.
IS21IS21 IS21 Lecture 13 – 2003/2004 2 Functional and Non-Functional Requirements at different levels of abstraction I like this system, its fast and user friendly. User System Use the system Search for product I cant figure out how to do a search. The search takes ages. User System Learn about seller Order Product Make Complaint Fast Performance and User friendly interface required Intuitive Search Facility and fast processing time required.
IS21IS21 IS21 Lecture 13 – 2003/2004 3 Example: Boundary, Control and Entity Classes Member Sign on to System : Member : Security Screen 1. Sign on( ) : Security Check 2. Check Details( ) A typical System Use Case Basic Flow of Events realised as an Analysis Model Collaboration Diagram Example User Interface for the Security Screen Boundary Class : ID and Password Data 3. Check Valid( )
IS21IS21 IS21 Lecture 13 – 2003/2004 4 Business Process Modelling with Activity Diagrams An alternative approach for modelling business processes is to use activity diagrams. Swimlanes can be used for Actors and Business Workers.
IS21IS21 IS21 Lecture 13 – 2003/2004 5 Careful Planning Getting the right people (and only the right people) in the room. A well organised and tight agenda. Preparing all parties (Background Reading, expectations). Avoiding or engaging in Pre-meeting politics. Joint Requirements Planning Workshops II Follow Up Outputs need to be typed as documents or photographed. Circulated for all to agree. Actions Agreed should be minuted and then tracked by a project manager. Follow up workshops planned.