You are on page 1of 7

CSE4006: Software Engineering

Lab 4.Requirements Meeting


Software Engineering Lab

Except where otherwise noted, the contents of this document are Copyright 2017 Youn-geun Ahn and Scott
Uk-Jin Lee All rights reserved. Any redistribution, reproduction, transmission, or storage of part or all of the
contents in any form is prohibited without author’s expressed written permission.
Topic Discussion
Feedback

1. Please tell about your team project topic.

2. Other teams give feedbacks to them.


Exercise 1. Req Meeting(TW)
Role Playing 1: Requirements Gathering
1. Assign roles Customers / Developers.

2. Customers tell your requirements(or user story)


regardless of your knowledge about development.

3. Developers draw out more specific requirements


(including non-functional requirements) using questions
and gather them .
(e.g. Should it work on both Android and iPhone?)

4. Make meeting minutes.


Exercise 1. Req Meeting(TW)
Team Meeting

1. Review and analyze requirements(or user stories) which


elicited from the meeting.

2. Organize them with possibility, importance, risk(or other


aspects).

3. Make meeting minutes.


Exercise 1. Req Meeting(TW)
Role Playing 2: Requirements Negotiating

1. Switch the roles Customers / Developers.

2. Developers explain possibilities or importance


(or any other aspects) of the requirements.

3. Customers insist your opinion.


(e.g. This functionalities must have to contain.)

4. Make Meeting Minutes.


Exercise 1. Req Meeting
Submission

Upload meeting minutes at team Git repository.


(At least 3 meeting minutes, but more additional meetings are OK)

Invite TA(AhnYounGeun) to team Git repository.

* Please keep them organized.


Tips
• You will propose your team project at 4/5
• Your project should contains:
• Creativity
• Reality
• Profitability
• Originality
• Specific Planning(e.g. Milestones, WBS, Gantt …)
• Specific Requirements
• Attractive

You might also like