27-02-2013, 02:42 PM
University Record System (URS)
University Record.pdf (Size: 52.13 KB / Downloads: 62)
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.
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.
Use Case Diagrams
A set of ACTORS : roles users can play in
interacting with the system.
An actor is used to represent something that users
our system.
A set of USE CASES: each describes a possible
kind of interaction between an actor and the
system.
Uses cases are actions that a user takes on a system
A number of RELATIONSHIPS between these
entities (Actors and Use Cases).
Relationships are simply illustrated with a line
connecting actors to use cases.
Identify Classes (Extract Nouns)
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.