Software Engineering Course Lab Assignment Mastering Technic

software Engineering Courselab Assignmentmastering Technical Skill

Design and develop five prescribed Software Engineering (SE) diagrams using five different modern Computer-Aided Software Engineering (CASE) systems. For each diagram, use only one CASE system to create it. The diagrams include a Use Case diagram (or Activity SwimLane diagram), Class Objects diagram, Context Data Flow Diagram (DFD), Level-0 DFD, and State Transition Diagram (STD). Prepare a professional lab report in PPT and PDF formats, including screenshots of diagrams and the original diagram files, and submit as a ZIP or RAR archive containing all necessary components.

Paper For Above instruction

In this assignment, the focus is on mastering technical skills with modern CASE systems for system analysis and design modeling within a software engineering context. The goal is to develop proficiency in creating various types of SE diagrams using industry-relevant CASE tools, thereby enhancing your understanding of system design, visualization, and documentation techniques. This exercise also aims to produce high-quality professional documentation, integrating diagrams, screenshots, and explanatory content for comprehensive system analysis and design representation.

The assignment requires selecting five different CASE systems, each from the provided list: IBM Rational, SmartDraw, Microsoft Visio, Visual Paradigm Community Edition, and UMLet. You will create one specific diagram in each CASE tool, ensuring that each diagram type is represented only once per tool, thus covering all five prescribed diagrams. The diagrams to develop are:

  1. A Use Case diagram (or Activity or SwimLane diagram) illustrating actors and functions for the current Webster system, with detailed specifications such as at least 10 actors and 15 functions.
  2. A Class Objects (or Class) diagram describing at least 10 classes with attributes (including data types and lengths) and methods, capturing the current system structure.
  3. A Context Data Flow Diagram (DFD) showing the overall system interaction with at least 10 data entities, portraying data flows both from and to a single processing unit.
  4. A Level-0 DFD breaking down the main system functions into at least ten sub-functions, demonstrating detailed data flow and process relationships.
  5. A State Transition Diagram (STD) representing top-level activities such as enrollment or entry processes, with at least ten states and labeled events/actions.

Each diagram must be created in a specific CASE tool, with screenshots of the GUI and the diagram files in both original and PDF formats. The diagrams should be clear, with sufficiently large font sizes for readability. The final report must include a comprehensive PowerPoint presentation with a title slide, a table of contents, individual slides for each diagram set (with visual and PDF copies), and a concluding section with recommendations on suitable CASE systems for each diagram type. A justification for your system choices should be based on diagram complexity, usability, or other relevant criteria.

Organize all files into a single folder, compress it into a ZIP or RAR archive, and submit before the deadline. Ensure the archive is named appropriately following the course’s file-naming convention, and include all necessary files: the presentation, PDF diagrams, original diagram files, screenshots, and any other supporting documents. This systematic approach not only demonstrates your technical proficiency but also your ability to produce professional quality documentation, essential for real-world software engineering practice.

References

  • Booch, G., Rumbaugh, J., & Jacobson, I. (2005). The Unified Modeling Language User Guide. Addison-Wesley.
  • Ambler, S. (2003). The Object Primer: Agile Model-Driven Development with UML 2.0. Cambridge University Press.
  • Pressman, R. S. (2014). Software Engineering: A Practitioner's Approach (8th ed.). McGraw-Hill Education.
  • Object Management Group. (2017). OMG Unified Modeling Language (UML) Version 2.5.1. OMG specifications.
  • Gilb, T. (2005). Competitive Engineering: A Handbook For Systems Selecting. Elsevier.
  • Larman, C., & Basili, V. R. (2003). Iterative and Incremental Development: A Brief History. IEEE Computer, 36(6), 47–56.
  • Rational Software. (2003). Rational Unified Process and UML. IBM Press.
  • De Marco, D., & Spence, S. (2002). UML Distilled: A Brief Guide to the Standard Object Modeling Language. Pearson.
  • Koskela, L. (2000). An Exploration towards a Production Theory and its Application to Construction. Technical University of Finland.
  • Harrold, M. (2007). The Role of UML and CASE Tools in Software Development. IEEE Software, 24(2), 55–63.

Related Assignments