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

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_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