UML教材:0公立大学注册系统文档.doc_第1页
UML教材:0公立大学注册系统文档.doc_第2页
UML教材:0公立大学注册系统文档.doc_第3页
UML教材:0公立大学注册系统文档.doc_第4页
UML教材:0公立大学注册系统文档.doc_第5页
免费预览已结束,剩余1页可下载查看

下载本文档

版权说明:本文档由用户提供并上传,收益归属内容提供方,若内容存在侵权,请进行举报或认领

文档简介

Steps in Object-Oriented Systems Analysis:1.Identify the business events and make an event table (Chapter 3)2.Identify the use cases and produce a use case diagram for the system (Chapter 4)3.Write a use case narrative describing the systems response to each business event (Chapter 4)4.Draw a system sequence diagram for each use case scenario (Chapter 4)5.Produce a domain model showing the concepts, attributes, and associations in the problem domain of the system (Chapter 5)6.Write a contract for each system operation (Chapter 5)1.Identify the business events and make an event table (Chapter 3)A.List of business events:(i)Department submits class schedule external(ii)Time to produce class schedule temporal(iii)Student registers for classes external(iv)Time to produce class roster temporal B.Event Table:Event Table for the University Registration SystemEvent NumberEvent DescriptionSystem InputActor Providing InputSystem OutputActor Receiving Output1.Department submitsclass scheduleDepartment Class ScheduleDepartment2.Time to produce class schedule.UniversityClassScheduleStudentDepartmentProfessor3.Student registers for classes.Registration RequestStudentStudent Class ListStudent4.Time to produce class roster.ClassRosterProfessor2. Identify the use cases and produce a use case diagram for the system (Chapter 4)A. List of use cases: (i)Submit Department Class Schedule (ii)Produce University Class Schedule(iii)Register for Classes(iv)Produce Class Roster B.List of Actors:(i)Student initiating and participating (ii)Department initiating and participating(iii)Professor participatingC.Use Case Diagram:3. Write a use case narrative describing the systems response to each business event (Chapter 4)Use case:Submit Department Class ScheduleActors:DepartmentPurpose:Record a department class schedule.Overview:The Department submits a schedule of the classes it will offer for the next term. Details of each section (department code, course number, section number, maximum number of seats, meeting time, meeting place, and instructor identifier) are recorded in the system.Type: EssentialPreconditions:Courses and instructors are known to the system.Postconditions:Department class schedule was saved in the system.Special Requirements:Department must get a system response within 8 seconds when each section is entered.Flow of EventsActor ActionSystem Response1. This use case begins when a Department submits its schedule for a term.2. The Department provides thedepartment code, course number, section number, maximum number of seats, meeting time, meeting place and instructor identifier for each section in the schedule.3. Records the section schedule information.4. On completion of entry of the schedule, the Department indicatesthat the schedule is complete.Alternative Flow of EventsLine 3: Invalid department code and course number entered. Indicate error. Return to Step 2.Invalid meeting place entered. Indicate error. Return to Step 2.Invalid meeting time entered. Indicate error. Return to Step 2.Invalid instructor identifier entered. Indicate error. Return to Step 2.Use case:Register for ClassesActors:StudentPurpose:Register a student for classes and record the students schedule.Overview:A Student requests the sections of class desired for a term. The system adds the Student to each section if there is space available. On completion, the system provides the Student with a list of the classes in which he or she is enrolled.Type: EssentialPreconditions:Class schedule must exist.Student is known by the system.Postconditions:Student was enrolled in the section.Special Requirements:Student must get a system response within 10 seconds.Flow of EventsActor ActionSystem Response1. This use case begins when a Student desires to register for classes.2. The Student provides the Students identifier and a list of the department code, course number, and section number for each section desired.3. Adds the student to the section if there are seats available.4. On completion of entry of the section requests, the Student indicates that the request is complete.5. Produces a student class list for the Student.6. The Student receives the studentclass list.Alternative Flow of EventsLine 3: Invalid department code and course number entered. In

温馨提示

  • 1. 本站所有资源如无特殊说明,都需要本地电脑安装OFFICE2007和PDF阅读器。图纸软件为CAD,CAXA,PROE,UG,SolidWorks等.压缩文件请下载最新的WinRAR软件解压。
  • 2. 本站的文档不包含任何第三方提供的附件图纸等,如果需要附件,请联系上传者。文件的所有权益归上传用户所有。
  • 3. 本站RAR压缩包中若带图纸,网页内容里面会有图纸预览,若没有图纸预览就没有图纸。
  • 4. 未经权益所有人同意不得将文件中的内容挪作商业或盈利用途。
  • 5. 人人文库网仅提供信息存储空间,仅对用户上传内容的表现方式做保护处理,对用户上传分享的文档内容本身不做任何修改或编辑,并不能对任何下载内容负责。
  • 6. 下载文件中如有侵权或不适当内容,请与我们联系,我们立即纠正。
  • 7. 本站不保证下载资源的准确性、安全性和完整性, 同时也不承担用户因使用这些下载资源对自己和他人造成任何形式的伤害或损失。

评论

0/150

提交评论