CSE403 Software Engineering Autumn 2001 CSE 403 Autumn 2001 CSE403 Software Engineering Autumn 2001 Gary Kimura Lecture #3 October 5, 2001 October 5, 2001

Today Project Introduction How do we break up the project Due via email today List of team members (email alias) List of top 3 project risks Due next Friday A weekly project report A draft of requirements specification (details on Monday)

Differences from previous projects Two years ago the students got too absorbed in the technical aspects of the problem Two years we let the groups wander through their own organizational issues Last year it was a more cut and dry requirements. Last year was too competitive This year communication and architecture design is even more vital Dictate either C, C++, or Java

Product requirements Needs a document listing the product requirement. Some necessary items are: Describe its general function and purpose Describe how it will be used by the customer Describe what is required for the customer Describe various aids to the customer Describe hardware and software requirements

Group Organization 22 students each Not everyone will write shipping code Manager, secretary, and group organizer (1 - 2) Program management (4 - 5) Software Developer (5 - 6) Tester (7 - 8) Documentation (3 - 4) In real world environments you sometimes work with people you can’t stand

Manager responsibilities Organizing the whole thing Ensuring that everyone knows their part and milestones Fostering communication within the group Keeping the schedule Understanding the whole project Not doing the work but knowing how each part fits in

Program Management responsibilities Defining the product Identifying customer needs Questioning the need or appropriateness of the design Working through all the usage scenarios Looking outside the “box”

Developer responsibilities Designing the architecture and coding the product Working with PM to ensure you are building what they defined Adding APIs as needed by the test group

Tester responsibilities Unit or component testing Correctness tests End cases Error checking Stress tests Independent code review leading to targeted tests Interaction with other systems

Documentation responsibilities Keeping track of all the design documentation Complete end user documentation Quick guides and on-line help.