UMLusecase

UMLusecase - UseCaseDiagrams 1 Introduction

Info iconThis preview shows pages 1–6. Sign up to view the full content.

View Full Document Right Arrow Icon
1 Use Case Diagrams 
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
2 Introduction Getting started is the most difficulty part of any  new process. In software modelling, the first thing you need  to do is understand what are you going to  model and ultimately develop. Creating a highest form details about a  system--use case diagram--is an almost natural  point of origin for the software design. A use case diagram is an excellent way to  communicate to management, customers, and  other non-development people what a system  will do when it is completed.
Background image of page 2
3 University Record System (URS) A University record system should keep information  about its students and academic staff. Records for all university members are to include their  id number, surname, given name, email, address, date  of birth, and telephone number.  Students and academic staff each have their own unique ID  number: studN (students), acadN (academic employee), where  N is an integer  (N>0).  In addition to the attributes mentioned above:  Students will also have a list of subjects they are enrolled in. A  student cannot be enrolled in any more than 10 subjects.  Academic employees will have a salary, and a list of subjects  they teach. An academic can teach no more than 3 subjects.
Background image of page 3

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
4 Some Actions Supported by URS The system should be able to handle  the following commands. Add and remove university members  (students, and academic staff) Add and Delete subjects Assign and Un-assign  subjects to students Assign and Un-assign subjects to academic  staff.
Background image of page 4
Use Case Diagrams Use Case diagrams show the various  activities the users can perform on the  system.  System is something that performs a  function. They model the dynamic aspects of the 
Background image of page 5

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Image of page 6
This is the end of the preview. Sign up to access the rest of the document.

This document was uploaded on 01/17/2012.

Page1 / 26

UMLusecase - UseCaseDiagrams 1 Introduction

This preview shows document pages 1 - 6. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online