Non Functional Requirements, Post Assignment Feedback-Software Engineering-Handout, Exercises of Software Engineering

This handout is feedback for assignment of Software Engineering. Teacher Sarmad Muneer explained our mistakes in this. It includes: Uploaded, Lms, Test, Cases, Improving, Grades, Assignment, Developed, Purpose

Typology: Exercises

2011/2012

Uploaded on 08/01/2012

ambuja
ambuja 🇮🇳

4.4

(5)

92 documents

1 / 2

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
Post Assignment Feedback: Spring 2012_CS504_1
Introduction:
Post assignment feedback consists of the detail explanation of the common
problems faced by students while preparing the assignment solution. This will help
students in better understanding the solution of the assignment.
Feedback:
Assignment No.{1} Software Engineering
(CS504)
Marks: 20 Due Date: 12/04/2012
Assignment Solution: Uploaded in lms.
Common Mistakes
& Explanation:
Mistake 1: Business requirement was written as either a paragraph or
numbered list of requirements.
Explanation: Business requirement is written in form of a single
statement which is actually vision of project.
Mistake 2: Non-functional requirements were written as user
requirements.
Explanation: User requirements are tasks that user must be able to
achieve while using the system. Where non functional requirements are
quality attributes or constraints. These include external system interfaces
constraints, design and implementation constraints, regulations,
standards, and contracts to which the product must conform and quality
and performance attributes.
Mistake 3: Context diagram was made by including all possible
modules.
Explanation: Context diagram depicts boundaries of system with
outside world. In this scenario, it should only show system interaction
with manager, data entry operator and account.
docsity.com
pf2

Partial preview of the text

Download Non Functional Requirements, Post Assignment Feedback-Software Engineering-Handout and more Exercises Software Engineering in PDF only on Docsity!

Post Assignment Feedback: Spring 2012_CS504_

Introduction:

Post assignment feedback consists of the detail explanation of the common problems faced by students while preparing the assignment solution. This will help students in better understanding the solution of the assignment.

Feedback:

Assignment No.{1} Software Engineering (CS504)

Marks: 20 Due Date: 12/04/

Assignment Solution: Uploaded in lms.

Common Mistakes & Explanation:

Mistake 1: Business requirement was written as either a paragraph or numbered list of requirements. Explanation: Business requirement is written in form of a single statement which is actually vision of project. Mistake 2: Non-functional requirements were written as user requirements. Explanation: User requirements are tasks that user must be able to achieve while using the system. Where non functional requirements are quality attributes or constraints. These include external system interfaces constraints, design and implementation constraints, regulations, standards, and contracts to which the product must conform and quality and performance attributes. Mistake 3: Context diagram was made by including all possible modules. Explanation: Context diagram depicts boundaries of system with outside world. In this scenario, it should only show system interaction with manager, data entry operator and account.

docsity.com

Mistake 4: Students were unable to identify entities for context diagram. Explanation: An entity may be defined as a thing which is recognized as being capable of an independent existence and which can be uniquely identified. An entity may be a physical object such as a house or a car, an event such as a house sale or a car service, or a concept such as a customer transaction or order. In context diagram, there were three entities; manager, accountant and data entry operator. Mistake 5: In interactions of context diagram, arrows were not labeled with corresponding inputs/outputs. Explanation: Since context diagram shows system interaction with outside world, so each interaction has some value either input (coming to the system) or output (coming out from the system). Purpose of Assignment 1: Purpose of assignment 1 was enabling students to understand project scope and identifying system’s stakeholders’ requirements. Visualization of proposed system interaction with outside world was another purpose. Instructor Comments: Software Engineering is not only a subject but a core methodology of developing software in industry. CS504 assignments will not only allow you to do final year project but a rehearsal for industry job. Overall result of assignment 1 shows that effort made by instructor did not go fruitless.

Overall Result of Assignment 1:

docsity.com