代做CSCI410 Software Requirements, Specifications and Formal Methods Autumn Session 2024代做Python语言

日期：2024-06-06 05:56

CSCI410

Software Requirements, Specifications and  Formal Methods

Autumn Session 2024

Subject Description

This subject demonstrates how software development can be viewed as a kind of engineering - an activity of   building useful things to serve recognisable purposes. The subject introduces students to the understanding of software requirements, techniques of requirement elicitation and analysis, and formal methods for software specification. The role of formal methods in the software development process is explained and investigated. The subject uses the Z notation as an example of a formal specification technique. Case studies are used as a basis for a study of the application of requirement processes and formal specification techniques. Topics will include: Introduction to the procedure of software requirement engineering, formal approaches to design and specification, review of mathematical foundation for formal methods, use of assertions and proof, analysis and verification of specification and design, disciplined approaches to design change, Z notation and other Morden methods for formal specification.

Subject Learning Outcomes

On successful completion of this subject, students will be able to:

1.    Describe state of the art techniques of software requirements elicitation and analysis.

2.    Explain how software system requirements are translated to appropriate software specifications expressed in a range of different formalisms.

3.    Analyse a representative software engineering problem and develop an appropriate formal specification using Z notation.

4.    Identify circumstances requiring formal software engineering techniques.

5.    Verify the correctness of a formal specification.

Assessment Summary

No.	Assessment Name	Assessment Weight	Mapping to Subject Learning Outcome	Task Due
1	Assignment	10%	SLO1, SLO4	31 Mar 2024 (Sunday in Session Week 5) Final submission time: 11:30pm
2	Project	30%	SLO2, SLO3, SLO4, SLO5	26 May 2024 (Sunday in Session Week 12) Final submission time: 11:30pm
3	Final Exam	60%	SLO1, SLO2, SLO3, SLO4, SLO5	The final exam will be held during the UOW exam period. Students will receive a SOLSmail  advising full details of the delivery format, time, and date of the final exam as they become available in the SOLS Exam Timetable.

Detailed assessment information is available in Section B of the subject outline.

Student Workload

Students should note that UOW equates 1 credit point to around 1.5 - 2 hours of study per week, including

lectures and tutorials/workshops/practicals, self-directed study and work on assessment tasks. For example, in a

6 credit point subject requires that students commit about 9 - 12 hours study a week, including attendance at lectures and tutorials.

Subject Changes and Response to Student Feedback

The School is committed to continual improvement in teaching and learning and takes into consideration student feedback from many sources. These sources include direct student feedback to tutors and lecturers, feedback through  Student  Services  and  the  Faculty  Central,  and  responses  to  the  Subject  Evaluation  Surveys.  This information is also used to inform. comprehensive reviews of subjects and courses.

* Update the lecture notes

* Update the assignments and lab exercises specification

Extraordinary Changes to the Subject Outline

In extraordinary circumstances the provisions stipulated in this Subject Outline may require amendment after the Subject Outline has been distributed. All students enrolled in the subject must be notified and have the opportunity to provide feedback in relation to the proposed amendment, prior to the amendment being finalised.

Learning Analytics

"Where Learning Analytics  data  (such  as  student  engagement  with  Moodle,  access to recorded lectures, University Library usage, task marks, and use of SOLS) is available to the Subject Coordinator, this may be used to assist in analysing student engagement, and to identify and recommend support to students who may be at risk of failure. If you have questions about the kinds of data the University uses, how we collect it, and how we protect your privacy in the use of this data, please refer tohttps://www.uow.edu.au/about/privacy/index.html ".

Your Privacy - Lecture Recording

In accordance with the Student Privacy & Disclosure Statement, when undertaking our normal teaching and learning activities, the University may collect your personal information. This collection may occur incidentally during the recording of lectures in equipped venues (i.e., when your identity can be ascertained by your image, voice or opinion), therefore the University further advises students that:

•    Lecture recordings are made available to students, university staff, and affiliates, securely on the   university's Echo360 ALP (Active Learning Platform) and via the subject Moodle eLearning site;

•    Recordings are made available only for which they were recorded, for example, as a supplemental study tool or to support equity and access to educational resources;

•    Recordings are stored securely for up to four years.

If you have any concerns about the use or accuracy of your personal information collected in a lecture recording, you may approach your Subject Coordinator to discuss your particular circumstances.

The University is committed to ensuring your privacy is protected. If you have a concern about how your

personal information is being used or managed please refer to the University's Privacy Policy or consult our Privacy webpagehttps://www.uow.edu.au/privacy/

Additional Information About This Subject

Not applicable.

ELEARNING, READINGS, REFERENCES AND MATERIALS

Subject eLearning

The University uses the eLearning system Moodle to support all coursework subjects. To access eLearning you must have a UOW user account name and password, and be enrolled in the subject. eLearning is accessed via SOLS (Student Online Service). Log on to SOLS and then click on the eLearning link in the menu column.

The University is committed to providing a safe, respectful, equitable and orderly environment for the University community, and expects each member of that community to behave responsibly and ethically. Students must comply with the University'sStudent Conduct Rulesand related policies including theIT Acceptable Use Policy andBullying Prevention Policy, whether undertaking their studies face-to-face or online. For more information on appropriate communication and etiquette in the online environment please refer to the guideOnline and Email Etiquette.

Major Text

There is no particular textbook in this subject.

Recommended Readings

Readings will be made available through the Moodle page for this subject

Students are encouraged to use the UOW Library catalogue and databases to locate additional resources including

the e-readings list:https://ereadingsprd.uow.edu.au/

References

[1] Phillip A. Laplante, Requirements Engineering for Software and Systems, Third Edition, Taylor & Francis Group, CRC Press, London New York, 2017

[2] J. M. Spivey, The Z Notation: A Reference Manual, Second Edition, Programming Research Group, University of Oxford

This is not an exhaustive list. Students are encouraged to use the UOW Library catalogue and databases to locate additional resources.

Other Resources

Van Lamsweerde, A., 2011. Requirements engineering. Wiley.

Mastering the Requirements Process, S. Roberson and J. Robertson, Addison-Wesley (1999).

Requirement Engineering: A good practice guide, Ian Sommerville & Peter Sawyer, Wiley (1998) CPT Tools: A tool for editiing, simulating, and analyzing Colored Petri Nets. https://cpntools.org/

Section B: Assessment

ASSESSMENT TASKS

Minimum Performance Requirements

To be eligible for a Pass in this subject a student must achieve a mark of at least 40% in the final exam (24/60).  Students who fail to achieve this minimum mark & would have otherwise passed may be given a TF (Technical Fail) for this subject.

Students who do not meet the minimum performance requirements, as specified for each assessment, will receive a TF (Technical Fail) grade for this subject, which will appear on your Academic Transcript.

Requirements Related to Student Contributions

Not applicable.

Referencing

Please consult the UOW Library website for further information:https://uow.libguides.com/refcite

Assessment Feedback

This resource explains feedback and overviews how to use feedback to improve your learning. Please refer to the UOW      Learning      Co-op      resource      for      students      on      'Understanding      assessment      feedback':

https://www.uow.edu.au/student/learning-co-op/assessments/understanding-assessment-feedback/

Detailed Assessment Information

Assessment 1
Assessment Name	Assignment	Assessment Type	Assignment
Weighting	10%
Subject Learning Outcomes Assessed	SLO1, SLO4	Individual or Group Assessment	Individual
Assessment Due	31 Mar 2024 (Sunday in Session Week 5) Final submission time: 11:30pm
Assessment Description and Criteria	• write a software requirement document using the IEEE template based on a given project description • identify the functional and non-functional requirements, the project domain, the stakeholdres, and the constraints of the project
Length / Duration	Week 2 ~ Week 5
Method of Submission	Online via Moodle
Return of Assessed Work	THE ASSIGNMENT MARK AND FEEDBACK WILL BE RETURNED TO STUDENTS WITHIN 2 WEEKS AFTER THE SUBMISSION VIA THE MOODLE SITE.