Thanks to visit codestin.com
Credit goes to www.scribd.com

Scribd
Upload
35 views9 pages

TMP3413 Software Engineering Lab: Lecture 00 - 2: Project's Proposal

This document outlines the guidelines for a software engineering project proposal. It discusses forming teams of 6-7 members with assigned roles, selecting a project title from an assessment document, and gathering requirements within 3 weeks. The proposal report should include an abstract, problem statement, objectives, scope, methodology, task allocation, goals, expected results, and planning. Teams must present their initial proposal in 15 minutes on October 11th-12th and submit a final proposal by October 18th-19th after making changes based on feedback. References for the project methodology and writing a proposal are also provided.

Uploaded by

Nurfauza Jali
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
35 views9 pages

TMP3413 Software Engineering Lab: Lecture 00 - 2: Project's Proposal

This document outlines the guidelines for a software engineering project proposal. It discusses forming teams of 6-7 members with assigned roles, selecting a project title from an assessment document, and gathering requirements within 3 weeks. The proposal report should include an abstract, problem statement, objectives, scope, methodology, task allocation, goals, expected results, and planning. Teams must present their initial proposal in 15 minutes on October 11th-12th and submit a final proposal by October 18th-19th after making changes based on feedback. References for the project methodology and writing a proposal are also provided.

Uploaded by

Nurfauza Jali
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
You are on page 1/ 9

TMP3413

Software
Engineering Lab

Lecture 00_2:
Project’s Proposal
Topic
 Team/Group formation
 Projectstitles
 Proposal report guidelines
 Proposal presentation
 References
Team / Group Formation
 Consist of 6 - 7 members per team.
 Assign each members with specific roles:

 Project manager  Customer interface manager


 Planning manager  Implementation manager
 Support manager  Test manager
 Quality manager  Process manager

 Each member can hold one or


two roles.
Project Titles
 Refer to project assessment document
 Within 3 weeks time to gather the requirements for
each domain and find the solution for every
problem statements.
 Extra marks for team who making effort to seek
requirements through interviews and observation.
Proposal Report Guidelines
 The proposal content:
 Abstract
 Problem statement
 Objectives
 Scope
 Software methodology
 Task Allocation
 Team Goals
 Expected Result
 Project planning

 Submission must be made before or on the 8th


October – Week 5 (Monday before 4:00 pm).
Proposal presentation
 Initial proposal presentation will be held on the 5th week
(11th/ 12th October).
 Project leader presents their proposal in 15 minutes.
 Changes will be made in 1 week time after the initial
presentation and advisable for each team to conduct
(weekly meeting) with their team members and
stakeholder (instructor or potential clients).
 The final Proposal must be submitted before the 6th
week (18th and 19th October).
Document Deliverables
Reference
 Watts S. Humphrey, TSP: Leading a Development Team by
Addison Wesley Professional (Part of the SEI Series in
Software Engineering series), 2006.
 W. Humphrey, T. Chick, W. Nichols, and M. Pomeroy-Huff,
"Team Software Process (TSP) Body of Knowledge (BOK),"
Software Engineering Institute, Carnegie Mellon University,
Pittsburgh, Pennsylvania, Technical Report CMU/SEI-2010-
TR-020, 2010.
 Ivan Marsic. “How to Write a Software Project Proposal.”
http://www.ece.rutgers.edu/~marsic/Teaching/SE/propos
al.html

You might also like