Page 1 of 5ITECH7410 Software Engineering MethodologiesAssessment 2 Individual Analysis and Design of a controlsystemOverviewThis assessment provides students with the opportunity to deepen, extend and apply theknowledge and skills developed from the first 3 weeks of material. Students complete theassignment individually.As described in this course’s third study guide – Software Analysis, Modelling and Specification –there are two main approaches to systems analysis specification – structured (or classical analysis)and object-oriented analysis. The reference text, Software Engineering: A Practitioners Approach(Pressman, 2010) identifies these two paths as different approaches to requirements modelling.There are special extensions to the structured approach to deal with real-time systems. Study guidethree identifies a real-time system as “…a system that has to respond to external events in a predefined maximum time interval. Hence such systems differ from the normal software system in thattheir temporal performance forms part of their requirements”.This assignment requires you to individually prepare parts of a requirements analysis specificationfor an example of a real-time system. You will be required to complete Data Flow Diagrams (DFDs)and include Real-Time Structured Analysis and Structured Design (RT-SASD) modifications andcomponents including Control Flow Diagram extensions (CFDs), where appropriate, ProcessSpecifications (PSPECs) and Control Specifications (CSPECs) (using combinational or sequentialFinite State Machines (FSMs) as required and presented in an appropriate format as ProcessActivation Tables (PATs) and/or State Transition (Machine) Diagrams (STDs) or State TransitionMatrices (STT)).Purpose, Learning OutcomesThe purpose of this assessment is to• demonstrate that you can conduct a search of literature related to Software EngineeringMethodologies in order to investigate appropriate models and methodologies for a particularproblem;• demonstrate that you can read the literature and understand how it is relevant to a particularproblem;• begin to collect some reference material that will be useful for your final seminar at the end ofthis course;• begin to use the library and Endnote to keep records of your research and summarise articlesfoundCRICOS Provider No. 00103D | RTO Code 4909CRICOS Provider No. 00103D | RTO Code 4909 Page 2 of 5• develop your skills, in particular, creating models and specifications of a system as amechanism for describing system requirements;• provide students with the opportunity to apply the knowledge and skills developed from thefirst three weeks of material;• provide students with an opportunity to perform an analysis of a system.The learning outcomes being directly assessed are:SkillsS1. Critically analyse and use complex decision making to research and determine the appropriateSoftware Engineering tools and methodologies to utilize for a given situation.S2. Apply professional communication skills to support and manage the engineering of a largesoftware system.S3. Review, critically analyse and develop artefacts to define processes for quality assurance, riskmanagement and communication in large software development projects.S4. Implement quality assurance activities to verify user requirements and validate designdecisions.Application of knowledge and skillsA1. Analysis of a large system development problem to decide upon the best methodologicalapproach.RequirementsIn this assignment, you are asked to create a requirements specification and analysis of part of asystem. The specification of the (sub) system should be a clear and unambiguous description of all therequirements, so that it could be used to inform a subsequent design of that system. As part of thesoftware engineering methodology, it is important that requirements are clearly specified so that theycan be traced through to design, verification and validation activities. Ultimately, if the system isspecified clearly, quality assurance activities can be adopted to ensure that the correct system is beingdeveloped.In the book “Requirements Engineering for Software and Systems’ by Phillip A Laplante, 2011, CRCPress, the appendix (https://learning.oreilly.com/library/view/requirements-engineeringfor/9781420064681/chapter-54.html ) contains a brief Software Requirements Specification (SRS) fora smart home. This book is available through the online oreilly books (accessed online through thelibrary). The smart home is discussed in various places within that text. You may NOT directly usediagrams provided in that text in this assignment, however, you may find it useful to use those asreference models to assist in your understanding of the analysis process.References provided in the course lecture slides will also be useful for additional reading.You are asked to select a particular control subsystem of an imagined smart campus system, toconduct a real-time structured analysis upon. It is recommended that each student selects a differentsubsystem to analyse. In the next assignment you will work in groups to produce some designartefacts working with other students. That subsequent group assignment will build on the workcompleted in this assignment.As part of your analysis, you are required to create the following analysis artefacts to specify thesystem requirements:CRICOS Provider No. 00103D | RTO Code 4909 Page 3 of 51. Data Flow (DFD) and Control Flow Diagrams (CFD) using real-time extensions forcontrol flows to indicate control events/flows, providing PSPECS where appropriate.These diagrams should be provided sufficient detail that only a single task is carried outby each process at the lowest level. You should show the control events/flows and dataflows on the same diagrams. Use the real-time extensions for control flows etc. shown inthe lecture notes. You need to determine when and where events will occur. Forexample, whenever a piece of data becomes available it may need a control event to letthe system know that it is available. These events must be clearly shown in theseDFD/CFD diagrams and then handled in the CSPEC.2. Process specifications (PSPECs) – a pseudo-code or similar design languagespecification is required for each process at the lowest level. A narrative descriptionalone will not be considered sufficient.3. Control Specifications (CSPECs) – use combinational or sequential Finite StateMachines (FSMs) as required, presented in an appropriate format. The idea is that theCSPEC will completely describe how a particular event or control flow is handled in thesystem. You need to provide at least one “Process Activation Table” and “StateMachine Diagram” as appropriate. The Finite State Machine (FSM) is used to describeevents and states in the system. The Process Activation Table/State Transition Table orState Transition Matrix should clearly demonstrate the valid transitions between states.Submit a detailed technical document that could be considered to contribute to an SRS document. Inaddition to the above, Your technical report should contain:1. Scope statement outlining the purpose of this report2. A complete description of the subsystem you are analysing describing the real timefunctionality and user interaction with the system3. Artefacts/models as describe above with supporting PSPECs and description explaining howthey contribute to the requirements analysisReasonable assumptions may be made about your system. These should be clearly stated in yourdescription of the subsystem.This is an individual assignment and students must submit it in Moodle.Timelines and expectationsPercentage value of this assessment: 20%Minimum time expectation: 12 hoursThis is an individual assignment and students must submit to Turnitin prior to submissionDue date and submission details are in the course description.Please refer to the Course Description for information regarding late assignments, extensions, specialconsideration, and plagiarism. You are reminded that all academic regulations can be accessed via theCRICOS Provider No. 00103D | RTO Code 4909 Page 4 of 5university’s website, see: http://federation.edu.au/staff/governance/legal/feduni-legislation/fedunistatutes-and-regulationsAdditional supportStudents are reminded that there are supports available regarding writing, researching and generalacademic skills. Various sources of help are available at : https://federation.edu.au/currentstudents#Learning_and_study, https://studyskills.federation.edu.au/student-skills/ andhttps://federation.edu.au/library/student-resources .Tutorial 1 activities provide some initial ideas regarding referencing, research and accessing journalsthrough the library. In addition, students should consult http://studyskills.federation.edu.au/referencing/and use FedCite (https://federation.edu.au/library/student-resources/fedcite ) to ensure they arereferencing correctly.Students should write in an appropriate academic writing style. For more information, consult theresources available at: https://studyskills.federation.edu.au/student-skills/writing/academic-writingstyle/The following additional resources will assist you with this assignment:• Concepts of Real Time Systems (http://www.youtube.com/watch?v=rYeqygKAZoM) (This isalso the resource listed under that name in Week 3 of your Moodle shell)• Week 3 study materials including readings, lecture notes and up to Section 3 of study guidethree;• Chapter 7 – Requirements Modeling: Flow, Behavior, Patterns, and WebApps – of Pressman(2010);• Chapter 5 and 6 in Real-Time Systems Design and Analysis. Tools for the Practitioner 4thedition (2012) Phillip A LaPlante, Seppo J Ovaska IEEE press, https://onlinelibrary-wileycom.ezproxy.federation.edu.au/doi/pdf/10.1002/978111813660• Hatley and Pirbhai Extensions from http://www.embedded.com/design/prototyping-anddevelopment/4397706/The-Hatley-Pirbhai-Methods—Eight-Years-of-Lessons-Learned orhttp://m.eet.com/media/1171869/pirbhai%20methods%20-%20eight%20years%20of%20lessons%20learned%20.pdf• Requirements Engineering for software and systems (2011) Philllip A Laplante CRC Presshttps://learning.oreilly.com/library/view/requirements-engineering-for/9781420064681/Marking CriteriaWork will be assessed according to the details provided in the Marking Rubric on the following page.CRICOS Provider No. 00103D | RTO Code 4909 Page 5 of 5Marking Rubric StudentName and NoMarkerDateItemDescriptionMax.MarksStudentMarkDescription ofsubsystemA text-based description completely outlines the details of thechosen sub system – processes involved, the triggering eventsand the transitions between valid states in the system. Thisdescription matches the subsequent analysis artefacts provided25Data FlowDiagrams(DFD)A single process is displayed at the lowest level. Whenever databecomes available it needs to be displayed and handled in theCSPEC. All relevant processes are included and matches thedescription provided completely.15Control FlowDiagram(CFD)Using real-time extensions for control flow to show when andwhere data is available. All relevant control flows and processesare included.15ProcessSpecification(PSPEC)Pseudo-code (or similar design language) required for at leastone process at the lowest level – narrative alone is not sufficient.Include ID.15ControlSpecifications(CSPEC)CSPECSs should describe how a chosen event or control flow ishandled in the sub-system. At least one of Process ActivationTables and State Machine Diagrams/Matrix are required.15Report styleandpresentationReport is well written using professional language and adheresto guidelines given for assignment and stated athttps://federation.edu.au/current-students/learning-andstudy/online-help-with/study-skills-and-writing-guides (Anyassumptions must be clearly stated and appropriate)15Total Mark100Course Mark20Comments:
