CIS 339 GUIDE Learn by Doing/cis339guide.com

1
CIS 339 GUIDE Learn by Doing/cis339guide.co
m
2
CIS 339 GUIDE Learn by Doing

• CIS 339 Entire Course (UOP)
• FOR MORE CLASSES VISIT
• www.cis339guide.com
•  
• CIS 339iLab 1 System Requirements
• CIS 339 iLab 2 of 7
• CIS 339iLab 3 - Structural Modeling - Class
  Diagram and CRCs
• CIS 339iLab 4 - Sequence, Communication, and
  State Diagrams
• CIS 339iLab 5 - Package Diagrams
• CIS 339iLab 6 - CRCs, Contracts, and Method
  Specifications
• CIS 339iLab 7 - Object-Oriented Application Coding

3
CIS 339 GUIDE
Learn by Doing

• CIS 339 iLab 1 System Requirements (Devry)
• FOR MORE CLASSES VISIT
• www.cis339guide.com
• L A B O V E R V I E W Scenario and Summary
• You have been hired by the School of Prosperity
  (SoP) as a software architect to help the school
  plan, design, and implement a new online system
  called the Student Records System (SRS).
• The Student Records System (SRS), described in
  the SRS Preliminary Planning Overview document,
  is the 7-week-long project that you will work on
  throughout this course. You will be developing
  UML models and documents for the planning,
  design, and implementation phases of SRS
  development.
• In each week, you will be provided with the
  information you need to continue to develop your
  analysis and design UML models and documents for
  this project.

4
CIS 339 GUIDE Learn by
Doing

• CIS 339 iLab 2 of 7 (Devry)
• FOR MORE CLASSES VISIT
• www.cis339guide.com
• Use Case Diagram and Use Case Description
• Work has already started on the planning phase of
  the Student Record System (SRS) for the School of
  Prosperity (SoP) and everyone is excited about
  this new system.
• As the software architect of this project, you
  met with many users and stakeholders of the old
  system to determine the requirements of the new
  Internet-accessible SRS software system. Your
  meetings and requirement-gathering efforts
  resulted in an SRS Requirement Definition
  document that summarizes all of the requirements
  of the project.

5
CIS 339 GUIDE Learn by
Doing

• CIS 339 iLab 3 - Structural Modeling - Class
  Diagram and CRCs (Devry)
• FOR MORE CLASSES VISIT
• www.cis339guide.com
•  
• As the software architect for the SRS system, you
  are making good progress in your work. After
  finishing the Functional Modeling (activity
  diagram, use case diagram, and use case
  descriptions) of the SRS system, you are now
  ready to move on to its Structural Modeling.
• In this week, you will use the models of your
  Functional Modeling to determine and design your
  class diagram and complete a CRC card for each
  class. The Structural Modeling is very critical
  for the success of your project since it is the
  backbone upon which the entire project is built,
  so take the time to design and refine your class
  diagram and its corresponding CRC cards.

6
CIS 339 GUIDE Learn by
Doing

• CIS 339 iLab 4 - Sequence, Communication, and
  State Diagrams (Devry)
• FOR MORE CLASSES VISIT
• www.cis339guide.com
•  
• In this week, you will use your functional and
  structural models as the basis for your
  behavioral models that need to be developed for
  the SRS system. Specifically, your deliverables
  for this week are designed to develop these two
  behavioral diagrams for the Register a Student
  for Classes use case.
• Sequence diagram Communication diagram
• In addition, you will also need to create a state
  machine diagram for the Registration class (the
  class that maintains the registration of a
  student in a class).

7
CIS 339 GUIDE Learn by
Doing

• CIS 339 iLab 5 - Package Diagrams (Devry)
• FOR MORE CLASSES VISIT
• www.cis339guide.com
•  
• Your analysis phase of the SRS project went well
  and your team feels good about their Functional,
  Structural, and Behavioral models. You also
  discussed the result of your analysis with the
  School of Prosperity (SoP) administration and
  they seem to be in line with your analysis
  models.
• Now is the time to start the design phase where
  you generate specific directions for the
  implementation of the system by the software
  development group. The first step in the design
  phase is to examine the SRS class diagram and to
  try to simplify its organization using a package
  diagram. The package diagram ensures that classes
  that belong together are grouped into a single
  package and thus simplify the development of
  these classes and their maintenance.

8
CIS 339 GUIDE Learn by
Doing

• CIS 339 iLab 6 - CRCs, Contracts, and Method
  Specifications (Devry)
• FOR MORE CLASSES VISIT
• www.cis339guide.com
• You decided to use the CourseList and the Course
  classes for your demonstrations. The CourseList
  class maintains and populates the current list of
  courses that the end user is working with while
  registering for clases. You will demonstrate the
  contract and the specification of the
  GetCourseByCourseID() of the CourseList class.
• The GetCourseByCourseID() method searches the
  current list of courses for a course whose
  CourseID matches the ID supplied to the method.
  If a matched course is found, it is returned by
  the GetCourseByCourseID() method otherwise a
  null value is returned, indicating there are no
  matching courses.

9
CIS 339 GUIDE Learn by
Doing

• CIS 339 iLab 7 - Object-Oriented Application
  Coding (Devry)
• FOR MORE CLASSES VISIT
• www.cis339guide.com
• Your demonstrations of how to create both method
  contract and the method specification for the
  GetCourseByCourseID() method of the CourseList
  class were very well received by your team
  members. They then asked you for one final
  demonstration of how to implement the method
  specification using an object-oriented (OO)
  programming language and see the method actually
  execute.
• You realize that it is easy to implement the
  method specification in an OO programming
  language, but it is hard to test it because the
  rest of the application is not developed yet. You
  decided, therefore, to write two pieces of code.

10
CIS 339 GUIDE
Learn by Doing