http://forums.visual-paradigm.com/posts/9.html JForum - http://www.jforum.net
Towards the end of each year, the Syllabus Committee in the Department of Computing determines which modules will be available to the second year (Y2)students in their following year. At the end of each academic year, the Head of Department allocates duties to members of the teaching staff and other staff. We assume that one lecturer is assigned and will teach only one module from the set of modules, which are to be available the next year. Each lecturer updates the course handbook entry for his/her module. The Y3 coordinator updates other parts of each handbook, checks the module entries produced by the lecturers, and produces the
electronic version of the course handbooks. Somebody in the Teaching Office (TO) produces a paper version of each course handbook. The Y2 coordinator is supposed to give the list of students entering Y3 from Y2 both to the Y3 coordinator and to the TO. The TO keeps the master list of all Y3 students. Each student is advised by a member of staff acting as a Director of Studies (DoS). A DoS is assigned to a student in their first year of study and remains in the role until they leave. Students rovisionally register for modules by filling in paper forms and handing them in to the TO. The TO checks that every student is registered for a reasonable set of modules.
1. Perform a Domain Analysis and derive a conceptual level Class
Diagram.
2. Define what the components of a Use-case Diagram are, and explain
how these components can be identified.
3. Derive the Use-case Diagrams and describe in detail at least 3 of the
use-cases.
4. Derive the Activity Diagrams from your related use-cases.
5. Derive a detailed Class Diagram including attributes, operations and
any other relevant features.
6. Model the behaviour of the class objects that communicate with each
other with Sequence and Communication Diagrams.
7. Derive the State Diagrams for more than one of your class objects.
]]> http://forums.visual-paradigm.com/posts/2643#20110.html http://forums.visual-paradigm.com/posts/2643#20110.html Anonymous wrote:

this is to devolop a system to help the computer science department of a university administer its final year undergraduate courses.you have the following description of the departmental procedures. Towards the end of each year, the Syllabus Committee in the Department of Computing determines which modules will be available to the second year (Y2)students in their following year. At the end of each academic year, the Head of Department allocates duties to members of the teaching staff and other staff. We assume that one lecturer is assigned and will teach only one module from the set of modules, which are to be available the next year. Each lecturer updates the course handbook entry for his/her module. The Y3 coordinator updates other parts of each handbook, checks the module entries produced by the lecturers, and produces the electronic version of the course handbooks. Somebody in the Teaching Office (TO) produces a paper version of each course handbook. The Y2 coordinator is supposed to give the list of students entering Y3 from Y2 both to the Y3 coordinator and to the TO. The TO keeps the master list of all Y3 students. Each student is advised by a member of staff acting as a Director of Studies (DoS). A DoS is assigned to a student in their first year of study and remains in the role until they leave. Students rovisionally register for modules by filling in paper forms and handing them in to the TO. The TO checks that every student is registered for a reasonable set of modules. 1. Perform a Domain Analysis and derive a conceptual level Class Diagram. 2. Define what the components of a Use-case Diagram are, and explain how these components can be identified. 3. Derive the Use-case Diagrams and describe in detail at least 3 of the use-cases. 4. Derive the Activity Diagrams from your related use-cases. 5. Derive a detailed Class Diagram including attributes, operations and any other relevant features. 6. Model the behaviour of the class objects that communicate with each other with Sequence and Communication Diagrams. 7. Derive the State Diagrams for more than one of your class objects.

]]> http://forums.visual-paradigm.com/posts/2643#26880.html http://forums.visual-paradigm.com/posts/2643#26880.html Anonymous wrote:

Anonymous wrote: this is to devolop a system to help the computer science department of a university administer its final year undergraduate courses.you have the following description of the departmental procedures. Towards the end of each year, the Syllabus Committee in the Department of Computing determines which modules will be available to the second year (Y2)students in their following year. At the end of each academic year, the Head of Department allocates duties to members of the teaching staff and other staff. We assume that one lecturer is assigned and will teach only one module from the set of modules, which are to be available the next year. Each lecturer updates the course handbook entry for his/her module. The Y3 coordinator updates other parts of each handbook, checks the module entries produced by the lecturers, and produces the electronic version of the course handbooks. Somebody in the Teaching Office (TO) produces a paper version of each course handbook. The Y2 coordinator is supposed to give the list of students entering Y3 from Y2 both to the Y3 coordinator and to the TO. The TO keeps the master list of all Y3 students. Each student is advised by a member of staff acting as a Director of Studies (DoS). A DoS is assigned to a student in their first year of study and remains in the role until they leave. Students rovisionally register for modules by filling in paper forms and handing them in to the TO. The TO checks that every student is registered for a reasonable set of modules. 1. Perform a Domain Analysis and derive a conceptual level Class Diagram. 2. Define what the components of a Use-case Diagram are, and explain how these components can be identified. 3. Derive the Use-case Diagrams and describe in detail at least 3 of the use-cases. 4. Derive the Activity Diagrams from your related use-cases. 5. Derive a detailed Class Diagram including attributes, operations and any other relevant features. 6. Model the behaviour of the class objects that communicate with each other with Sequence and Communication Diagrams. 7. Derive the State Diagrams for more than one of your class objects.

]]> http://forums.visual-paradigm.com/posts/2643#26882.html http://forums.visual-paradigm.com/posts/2643#26882.html