310313 REQUIREMENTS CAPTURE 1 ASU Course Registration Domain Model.

Slides:



Advertisements
Similar presentations
ER Model For a college DB
Advertisements

ISIS Registration.
Use case tutorial examples.
CLASS REGISTRATION Grade 11. VIEWING COURSE DESCRIPTIONS ONLINE The registration handbook is available on the Aitkin Public Schools website ISD1.org.
CLASS REGISTRATION Grade 12.
Use Class Search if you don’t know the class number.
CLASS REGISTRATION Grade 8 to 9. VIEWING COURSE DESCRIPTIONS ONLINE The registration handbook is available on the Aitkin Public Schools website.
Pre-Enrollment Spring Pre-Enrollment Packet Letter to Parents Commonly Asked Questions Transcript Concurrent Enrollment Information Course Description.
SwE 313 Case Study Registration System.
Close Registration Brief Description
Sample Analysis Model. Example: Sequence Diagram –“Richer Sample.” : Student : RegisterForCoursesForm : RegistrationController : Schedule : Student :
1. Print the Degree Audit 2. Use the Wizard to Add Courses 3. Use Catalog Search and Add 4. Re-print the Degree Audit 5. Contact your Advisor 6. Register.
1 Registering for Classes Using MyUAlbany Advisement Services Center.
BLC Training for Instructors Presented By: Banner Health Learning & Development Team.
The Registration Experience Student Registration via Self-Service.
Instruction on how to complete a Web TA Request
REQUIREMENTS CAPTURE 1 ASU Course Registration System User Interface Specifification UI Elements Register for courses Use Case.
® IBM Software Group © 2006 IBM Corporation Writing Good Use Cases Module 4: Detailing a Use Case.
Faculty Center for Instructors and Roster Contacts Roles and Access Faculty Center Features Grade Changes and Approval.
COURSE ADDITION CATALOG DESCRIPTION To include credit hours, type of course, term(s) offered, prerequisites and/or restrictions. (75 words maximum.) 4/1/091Course.
IT Websites What you’re expected to know…. Websites to be covered IThink.ou.edu pay.ou.edu it.ou.edu studentservices.ou.edu alerts.ou.edu support.ou.edu.
Use Case modelling 1. Objectives  Document user requirements with a model  Describe the purpose of an actor and a use case  Construct a use case model.
Drop-In Course Registration Review Class Registration TUTORIAL.
COMP 211 REQUIREMENTS CAPTURE 1 ASU Course Registration Acceptance Test Plan (Inception Phase)
Requirements Analysis Visual Modeling] Lab 02 Visual Modeling (from Visual Modeling with Rational Rose and UML) A way of thinking about problems using.
REQUIREMENTS CAPTURE 1 ASU Course Registration System Use-case Model Actor.
SCHOOL NAME
Specifying Software Component Frameworks using UML and OCL H. Conrad Cunningham Yi Liu Software Architecture Research Group Dept. of Computer & Information.
The Hong Kong University of Science and Technology COMP3311 Spring 2013 Tutorial 1 ER Diagrams.
Conceptual Model or Domain Models Chapter10 Applying UML and pattern.
ASU Course Registration System System Analysis Communication Diagram Use Case: Select Courses to Teach.
FAST STUDENT Your Chance to Learn!. Objectives for today’s course Show you what we think is new & exciting in FAST Student Demo of some new functionality.
COMP231 Tutorial 1 ER Model and ER to Relational Schema.
REQUIREMENTS CAPTURE 1 ASU Course Registration System Use-case Model.
Faculty Center for Instructors and Roster Contacts Roles and Access Faculty Center Features Grade Changes and Approval.
1-1 Chapter 1 Databases and Database Users 1.1 Introduction 1.2 An Example 1.3 Characteristics of the Database Approach 1.4 Actors on the Scene 1.5 Workers.
Northwest Nazarene University introduces PDLearn The CPD’s web access course selection and registration system for students and instructors Instructor.
Class Scheduler Team Members Bernard Battle Jerad Blake James Knoch Chris Louallen Lenora Pride.
ONLINE CREDIT RECOVERY PROGRAM
REGISTRATION PROCESS Must have an ID number + password (DOB) Format- YYYYMMDD To ADD COURSES- Select courses by first selecting the CORRECT SEMESTER then.
Undergraduate Academic Advising Registration At October 2015.
Essentials of Visual Modeling w/ UML Instructor Notes
More DFDs Class 12.
REQUIREMENTS CAPTURE 1 ASU Course Registration Domain Model.
ONLINE COURSE REQUEST HIGH SCHOOL IMPLEMENTATION JANUARY 2016.
Faculty Center for Instructors Roles and Access Faculty Center Features Grade Changes and Approval.
ACO 101: Use cases What do the users do?. When building a system You begin with the Use Case Analysis – When looking at the system as a whole, Use Case.
Create a Study Abroad Section
Schedule of NTUST course selection 2017 Fall
ONLINE COURSE REGISTRATION
Entity-Relationship Modeling
UML SEQUENCE AND CLASS DIAGRAMS
HIGH SCHOOL IMPLEMENTATION
Step 3 Register for Classes
Kentwood Registration -Juniors
Getting Ready for Registration
Example A university registrar’s office maintains data about the following entities: (a) courses, including number, title, credits, syllabus, and prerequisites;
Registration February 27– March 9, 2017
for Instructors and Roster Contacts
Marvel College Appendix A.
for Instructors and Roster Contacts
Faculty Center for Instructors and Roster Contacts.
for Instructors and Roster Contacts
Mount Si High School Grade 11
It’s time to plan for your Sophomore year !
Faculty Center for Roster Contacts
Faculty Center for Instructors
Faculty Center for Roster Contacts
Advising California State Polytechnic University, Pomona
Presentation transcript:

REQUIREMENTS CAPTURE 1 ASU Course Registration Domain Model

REQUIREMENTS CAPTURE 2 ASU — COURSE REGISTRATION PROBLEM STATEMENT At the beginning of each semester, students may request a course catalog containing a list of course offerings needed for the semester. Information about each course, such as instructor, department, and prerequisites are included to help students make informed decisions. The new system will allow students to select four course offerings for the coming semester. In addition, each student will indicate two alternative choices in case a course offering becomes filled or is canceled. No course offering will have more than forty students or fewer than ten students. A course offering with fewer than ten students will be canceled. Once the registration process is completed for a student, the registration system sends information to the billing system so the student can be billed for the semester. Professors must be able to access the online system to indicate which courses they will be teaching, and to see which students signed up for their course offerings. For each semester, there is a period of time that students can change their schedule. Students must be able to access the system during this time to add or drop courses.

REQUIREMENTS CAPTURE 3 ASU — POSSIBLE CLASSES At the beginning of each semester, students may request a course catalog containing a list of course offerings needed for the semester. Information about each course, such as instructor, department, and prerequisites are included to help students make informed decisions. The new system will allow students to select four course offerings for the coming semester. In addition, each student will indicate two alternative choices in case a course offering becomes filled or is canceled. No course offering will have more than ten students or fewer than three students. A course offering with fewer than three students will be canceled. Once the registration process is completed for a student, the registration system sends information to the billing system so the student can be billed for the semester. Professors must be able to access the online system to indicate which courses they will be teaching, and to see which students signed up for their course offerings. For each semester, there is a period of time that students can change their schedule. Students must be able to access the system during this time to add or drop courses.

REQUIREMENTS CAPTURE 4 ASU: POSSIIBLE CLASSES At the beginning of each semester, students may request a course catalogue containing a list of course offerings needed for the semester. classes: Semester, Student, CourseCatalogue, CourseOffering Information about each course, such as instructor, department, and prerequisites are included to help students make informed decisions. classes: Course (Information), Instructor, Department, Prerequisite, Informed Decision The new system will allow students to select four course offerings for the coming semester. classes: System In addition, each student will indicate two alternative choices in case a course offering becomes filled or is canceled. classes: AlternativeChoice

REQUIREMENTS CAPTURE 5 ASU: POSSIIBLE CLASSES No course offering will have more than forty students or fewer than ten students. classes: no new classes A course offering with fewer than ten students will be canceled. classes: no new classes Once the registration process is completed for a student, the registration system sends information to the billing system so the student can be billed for the semester. classes: RegistrationProcess, Information, BillingSystem Professors must be able to access the online system to indicate which courses they will be teaching, and to see which students signed up for their course offerings. classes: Professor

REQUIREMENTS CAPTURE 6 ASU: POSSIIBLE CLASSES For each semester, there is a period of time that students can change their schedule. classes: PeriodOfTime, Schedule Students must be able to access the system during this time to add or drop courses. classes: no new classes

REQUIREMENTS CAPTURE 7 ASU — KEEPIING THE RIIGHT CLASSES Semester  attribute (of course offering) Student  O.K. Course catalog  irrelevant (physical system generated entity) Course offering  O.K. Course (information)  O.K. Instructor  redundant (same as professor) Department  O.K. Prerequisite  role (of course) Informed decision  vague (mental process of students) System  implementation construct Alternative choice  redundant (same as course offerings) Registration process  operation (activity of using the system) Information  vague (need to specify more clearly) Billing system  irrelevant (external system) Professor  O.K. Period of time  vague (related to processing constraints) schedule  redundant (same as course offerings)

REQUIREMENTS CAPTURE 8 ASU — POSSIBLE ASSOCIATIONS At the beginning of each semester, students may request a course catalog containing a list of course offerings needed for the semester. Information about each course, such as instructor, department, and prerequisites are included to help students make informed decisions. The new system will allow students to select four course offerings for the coming semester. In addition, each student will indicate two alternative choices in case a course offering becomes filled or is canceled. No course offering will have more than ten students or fewer than three students. A course offering with fewer than three students will be canceled. Once the registration process is completed for a student, the registration system sends information to the billing system so the student can be billed for the semester. Professors must be able to access the online system to indicate which courses they will be teaching, and to see which students signed up for their course offerings. For each semester, there is a period of time that students can change their schedule. Students must be able to access the system during this time to add or drop courses.

REQUIREMENTS CAPTURE 9 ASU — POSSIBLE ASSOCIATIONS At the beginning of each semester, students may request a course catalogue containing a list of course offerings needed for the semester. associations: Student Requests CourseCatalogue CourseCatalogue Contains CourseOffering Semester Needs CourseOffering Information about each course, such as instructor, department, and prerequisites are included to help students make informed decisions. associations: CourseCatalogue Includes Course(Information) CourseCatalogue Helps Student Student Makes InformedDecision The new system will allow students to select four course offerings for the coming semester. associations: System Allows Student Student Selects CourseOffering

REQUIREMENTS CAPTURE 10 ASU — POSSIBLE ASSOCIATIONS In addition, each student will indicate two alternative choices in case a course offering becomes filled or is canceled. associations: Student Indicates AlternativeChoice ? Fills CourseOffering ? Cancels CourseOffering No course offering will have more than forty students or fewer than ten students. associations: CourseOffering Has Student A course offering with fewer than ten students will be canceled. associations: no new associations

REQUIREMENTS CAPTURE 11 ASU — POSSIBLE ASSOCIATIONS Once the registration process is completed for a student, the registration system sends information to the billing system so the student can be billed for the semester. associations: Student Completes RegistrationProcess System Sends Information To BillingSystem BillingSystem Bills Student Professors must be able to access the online system to indicate which courses they will be teaching, and to see which students signed up for their course offerings. associations: Professor Accesses System Professor Indicates Course Professor Teaches Course Professor Sees Student Student SignsUpFor CourseOffering

REQUIREMENTS CAPTURE 12 ASU — POSSIBLE ASSOCIATIONS For each semester, there is a period of time that students can change their schedule. associations: Student Changes Schedule Students must be able to access the system during this time to add or drop courses. associations: Student Accesses System Student Adds Course Student Drops Course

REQUIREMENTS CAPTURE 13 ASU — POSSIBLE ASSOCIATIONS student — requests — course catalog  class eliminated course catalog — contains — course offering  class eliminated semester — needs — course offering  class  eliminated course catalog — includes — course information  class  eliminated course catalog — helps — student  class  eliminated student — makes — informed decision  class  eliminated student — selects — course offering  operation student — indicates — alternative choice  operation ? — fills — course offering  operation ? — cancels — course offering  operation course offering — has — student  O.K. student — completes — registration process  class  eliminated system — sends — information — to — billing system  class  eliminated billing system — bills — student  class  eliminated professor — accesses — system  class  eliminated professor — indicates — course  operation professor — teaches — course  O.K. professor — sees — student  operation student — signs up for — course offering  operation student — changes — schedule  operation student — accesses — system  class  eliminated student — adds — course  operation student — drops — course  operation

REQUIREMENTS CAPTURE 14 ASU: DOMAIIN MODEL Classes Associations Student Department CourseOffering Has Student Course Professor Professor Teaches Course CourseOffering

REQUIREMENTS CAPTURE 15 ASU — DOMAIN MODEL prerequisite Student CourseOffering Teaches Appointed Offers ProfessorDepartment Course IsPrerequisiteFor EnrollsIn course Association information in red is inferred from domain knowledge.

REQUIREMENTS CAPTURE 16 ASU DOMAIN MODEL DETAIL— GENERALIZATION userID :String password : String userGroup : Integer surname : String otherNames : String address : String DOB : Date dateOfAdmission : Date levelOfStudy : String modeOfStudy : String yearOfStudy : Integer Student CourseOffering offeringId : String semester : String year : Integer Course code : String title : String description: String credits : Integer userID : String password : String userGroup : Integer surname : String otherNames : String address : String DOB : Date qualification : String Professor Department code: String title : String

REQUIREMENTS CAPTURE 17 ASU — DOMAIN MODEL DETAILS prerequisite Student CourseOffering Teaches AppointedIn Offers ProfessorDepartment Course IsPrerequisiteFor * * 1..* 1* * EnrolledIn grade : String 1..* Association information in red is inferred from domain knowledge. course

REQUIREMENTS CAPTURE 18 ASU Course Registration System Domain Model Detail Generalization

REQUIREMENTS CAPTURE 19 ASU DOMAIN MODEL DETAIL— GENERALIZATION userID :String password : String userGroup : Integer surname : String otherNames : String address : String DOB : Date dateOfAdmission : Date levelOfStudy : String modeOfStudy : String yearOfStudy : Integer Student CourseOffering offeringId : String semester : String year : Integer Course code : String title : String description: String credits : Integer userID : String password : String userGroup : Integer surname : String otherNames : String address : String DOB : Date qualification : String Professor Department code: String title : String

REQUIREMENTS CAPTURE 20 ASU DOMAIIN MODEL DETAIIL: GENERALIIZATIION

REQUIREMENTS CAPTURE 21 ASU DOMAIIN MODEL DETAIIL: GENERALIIZATIION

REQUIREMENTS CAPTURE 22 prerequisite ASU — COURSE REGISTRATION DOMAIN MODEL Student CourseOffering Teaches AppointedIn Offers ProfessorDepartment Course IsPrerequisiteFor * * 1..* 1* * 1 0..* EnrolledIn grade : String Person 1..*

REQUIREMENTS CAPTURE 23 ASU Course Registration System Domain Model Detail Constains

REQUIREMENTS CAPTURE 24 ASU DOMAIN MODEL DETAIL: CONSTRAINTS Is the multiplicity of the CourseOffering end of the EnrollsIn association realistic? –A student can enroll in at most four course offerings during their entire time at the university. Actually, the constraint should be: –A student can enroll in at most four course offerings in one semester. It is actually unknown the total number of course offerings in which a student will enroll. –The max-card should be *. To document the fact that enrollment in a semester should not be more than four course offerings an OCL constraint is needed.

REQUIREMENTS CAPTURE 25 ASU DOMAIN MODEL DETAIL: CONSTRAINTS