Data Flow Diagrams, Case Model, 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: Software, Engineering, Uml, Case, Model, Data, Store, Flow, Diagram, Notations, Description

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_2
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.{2} Software Engineering (CS504) Marks: 20 Due Date: 26/04/2012
Assignment Solution: Uploaded in lms.
Common Mistakes &
Explanation:
Mistake 1: Incorrect UML notations used in both the diagrams.
Explanation: Always use proper UML notations to represent different
components of a diagram. For example, if you are developing a Use Case
Model then always use ovals to represent use cases.
Mistake 2: Incorrect Use Cases included in the Use Case Model.
Explanation: It was found that most of the students did not have the idea of
how to identify use cases and then add in the diagram. Most of the students
used ambiguous names for the use cases. Each use case name must be self-
explanatory and it should explain the purpose which the use case serves in the
diagram.
Mistake 3: Illegal data flows were included in DFD.
Explanation: While drawing Data Flow Diagram, most students added a
direct data flow connection between External Agent and Data Store which is
illegal as explained in the handouts and lectures. Similarly, direct data flow
between two external agents is also illegal and same practice was repeated by
numerous students which should be avoided.
Always take special care of rules for drawing the Data Flow Diagram.
docsity.com
pf2

Partial preview of the text

Download Data Flow Diagrams, Case Model, 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.{2} Software Engineering (CS504) Marks: 20 Due Date: 26/04/

Assignment Solution: Uploaded in lms.

Common Mistakes & Explanation:

Mistake 1: Incorrect UML notations used in both the diagrams. Explanation: Always use proper UML notations to represent different components of a diagram. For example, if you are developing a Use Case Model then always use ovals to represent use cases. Mistake 2: Incorrect Use Cases included in the Use Case Model. Explanation: It was found that most of the students did not have the idea of how to identify use cases and then add in the diagram. Most of the students used ambiguous names for the use cases. Each use case name must be self- explanatory and it should explain the purpose which the use case serves in the diagram. Mistake 3: Illegal data flows were included in DFD. Explanation: While drawing Data Flow Diagram, most students added a direct data flow connection between External Agent and Data Store which is illegal as explained in the handouts and lectures. Similarly, direct data flow between two external agents is also illegal and same practice was repeated by numerous students which should be avoided.

Always take special care of rules for drawing the Data Flow Diagram.

docsity.com

Purpose of Assignment 1: Purpose of assignment 2 was to enable the students to learn how to draw Use Case and Data Flow models using system description and UML notations.

Instructor Comments: Throughout world, software development is carried out in almost way. CS assignment no. 2 will not only aid you to do final year project but a practice of job responsibilities of a software developer.

docsity.com