Lab
1
“Software Engineering” course
Lab Assignment
Mastering Technical Skills with Modern Computer Aided Software Engineering
(CASE) systems for System’s Analysis and Design Modeling
2
Lab Assignment Lab Assignment:
1. Learn, use and master technical skills with at least five (5) modern CASE systems (that are actively used in Software Development industry)
2. Design and develop high quality at least five (5) prescribed Software Engineering (SE) diagrams, and include them into Lab Report
3. Submit high quality professional Lab Report as a single ZIP or RAR file. It must include 1) PPT file and PDF file with PowerPoint presentation about main required Lab outcomes, and 2) files with all created SE diagrams in original and PDF formats as well as computer screen snapshots.
Modern CASE systems to learn and to use:
1. IBM Rational (commercial CASE system; however, it is available in Br160 Lab)
2. SmartDraw (commercial CASE system; however, it is available in Br160 Lab)
3. Microsoft Visio (commercial CASE system; however, it is available in Br160 Lab; additionally CS and CIS registered students can download it from playground server – see course website for details)
4. Visual Paradigm – Community Edition (free CASE system; it is available in Br160 Lab; additionally students can download it from the Internet – see course website for details)
5. UMLet (free CASE system; it is available in Br160 Lab; additionally students can download it from the Internet – see course website for details)
SE diagrams to develop and submit (see details on the next slides):
1. at least Use Case diagram (however, Activity diagram or even SwimLane diagram are preferred),
2. Data Object (DO) / Class Objects (CO) / Class diagram,
3. Context Data Flow Diagram (DFD),
4. Level-0 DFD, and
5. State Transition Diagram (STD).
Lab Video Tutorials available:
Visit course website and watch video tutorials about how to create SE diagrams in various CASE systems.
3
Lab Assignment (cont.) How many SE diagrams to design and develop?
Use only ONE CASE system to draw only ONE of the required SE diagrams given below. In other words, a “one-to- one” correspondence between SE diagrams and CASE systems should be used. It means “only one CASE system should be used to draw only one SE diagram”. As a result, a total of FIVE (5) CASE systems should be used in this lab to develop FIVE (5) PRESCRIBED SE diagrams.
A total of at least five (5) prescribed SE diagrams should be developed and presented in Lab Report and submitted to instructor.
TO DO list and parts of Lab Report:
Outcome 1: Use-Case diagram of the current Webster system (or, Activity Diagram for STUDENTS actor in the Webster, or SwimLane Diagram for several actors in Webster).
Draw Use Case diagram with
a) at least 10 actors (incl. 5 human beings and 5 non-human beings), and
b) at least 15 functions (relevant to selected actors).
Include into Lab_01 Report (this report is in a form of PPT presentation), slides with 1) computer screen snapshot (with visible CASE systems GUI) of final diagram, and 2) just created diagram in PDF format (with no system’s GUI). Be sure that font size used is enough for readers to read headings and names on the developed diagram.
Outcome 2: Class Objects (or, Class) diagram of the current Webster system
Draw Class Objects diagrams, including a) CO name, b) at least TEN (10) attributes, their data types and length of each attribute), and c) at least 5 methods for each CO, for at least 10 class objects in the current version of Webster, for example, Student, Course, Department Chair, etc.
Specify Data Type (integer, char, string, Boolean, etc.) for each attribute in CO.
Include into Lab_01 Report (this report is in a form of PPT presentation), slides with 1) computer screen snapshot (with visible CASE systems GUI) of final diagram, and 2) just created diagram in PDF format (with no system’s GUI). Be sure that font size used is enough for readers to read headings and names on the developed diagram.
4
Lab Assignment (cont.)
Outcome 3: Context Data Flow Diagram (DFD) diagram of the current Webster system
Draw Context Data-Flow Diagram (DFD) with ONE processing unit and at least TEN (10) data entities DE (i.e. class objects or actors), including at least 5 human being actors and at least 5 non-human being Des.
Provide at least 2 labeled data flows (i.e. legal methods of DE) from each DE to processing unit and at least 2 labeled arrows (i.e. legal methods of DE) from processing unit to each DE.
Include into Lab_01 Report (this report is in a form of PPT presentation), slides with 1) computer screen snapshot (with visible CASE systems GUI) of final diagram, and 2) just created diagram in PDF format (with no system’s GUI). Be sure that font size used is enough for readers to read headings and names on the developed diagram.
Outcome 4: Level-0 DFD diagram of the current Webster system
Divide the main function of Webster into at least TEN (10) sub-functions.
Draw Level-0 DFD with labeled sub-functions and corresponding data flows (i.e. arrows) in it.
Include into Lab_01 Report (this report is in a form of PPT presentation), slides with 1) computer screen snapshot (with visible CASE systems GUI) of final diagram, and 2) just created diagram in PDF format (with no system’s GUI). Be sure that font size used is enough for readers to read headings and names on the developed diagram.
Outcome 5: State Transition Diagram (STD) diagram of the current Webster system
Draw state transition diagram (STD) for the top-level activities (entry, enrollment, etc.) in Webster with at least TEN (10) stable states.
Label at least 2 events or 2 actions for each stable state.
Include into Lab_01 Report (this report is in a form of PPT presentation), slides with 1) computer screen snapshot (with visible CASE systems GUI) of final diagram, and 2) just created diagram in PDF format (with no system’s GUI). Be sure that font size used is enough for readers to read headings and names on the developed diagram.
5
Lab Assignment (cont.) WHAT to include in Lab Outcomes folder and how to submit it :
Create a folder with Lab outcomes – see an example of such a folder below. It should contain
1) PPT file and PDF file with PowerPoint presentation *) that contains all main required Lab outcomes, and
2) various files with all created SE diagrams in original (as in every CASE system) and in PDF formats as well as computer screen snapshots (PNG or JPEG)
See an example of such a folder below.
*) Requirements to PowerPoint presentation **):
specify name of each CASE system used to develop each diagram and include its logo;
Create the final PowerPoint presentation with
Title slide
Table of Content slide
Title slide for each set of slides that contains each type of developed SE diagrams in all formats as required in this course (see course web site for details)
Slide(s) with your recommendations (at the very of your report provide 1-2 slides with your recommendations about what CASE system(s) you recommend to be used to develop what types of SE diagrams; for example, IBM rational should be used to develop Class Objects diagrams – the best option, to develop Context DFD – the second best option, etc.)
**) A note: a web link to a fragment of very good Lab Report is available on course website
WHAT to submit and HOW to submit :
Be sure that your Lab folder contains all required files (see an example below)
Compress Lab folder with ZIP or RAR file compressor
Be sure that the name of your RAR or ZIP file follows the File Naming Convention (FNC) in this course (see details on course website)
One student team should submit the developed ZIP or RAR file only one time; Team Coordinator should do this on behalf of the entire team
Email your ZIP or RAR file to instructor BEFORE the designated deadline (see course web site for that deadline).
LATE SUBMISSIONS will be graded in accordance with the course LATE SUBMISSIONS POLICY (see course syllabus for details).
6
An example of Lab folder with various required files
An example of proper files in Lab folder An example of properly named ZIP file with all Lab required outcomes.
It should be submitted to instructor by email (as an attachment) BEFORE designated submission deadline