1 / 8

CSCI 506 Management of the Software Development process

CSCI 506 Management of the Software Development process. Phase 0 Aug.27, 2008. Based on. Team work technicalities. Goals. Assign team roles. Background and experience. Meetings schedule. Availability and workload. Means of communication. Fast and practical approach.

fisk
Télécharger la présentation

CSCI 506 Management of the Software Development process

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. CSCI 506 Management of the Software Development process Phase 0 Aug.27, 2008

  2. Based on Team work technicalities Goals • Assign team roles • Background and experience • Meetings schedule • Availability and workload • Means of communication • Fast and practical approach • Company name (logo)‏ • Brainstorming • Initial ideas about the team project • ..in progress

  3. Team name – KS3 (working name)‏ • Stephen Gregory – Leader3 yrs. as Software Engineer at Orchard Software Corporation. Experience with Java, C, C++, MSSQL • Kambiz Behbahani • 5 yrs. as EE at Honeywell , in Automation projects with PLC, EEBS degree from Purdue University-2007, Languages VB,C,C++. Currently work as Software Engineer I at Raytheon   • Seema Patil • 2 yrs. in TCS India. Has helped in creating an rough estimate proposal Cadbury's USA project.. • Shpetim Latifi • 1 yr TA in Computer Networks, Net. Architecture and Wireless networks research interest, ASP.NET, C#, MSSQL, Oracle

  4. Accomplishments • Set meeting schedule • Each Monday, 20 minutes before class • Alternate time before Wednesday's class • Set Current commitment level • Initially spend 4 hrs/wk on team work/project • Created Google Code & Google Group sites. • Created document templates for future deliverables

  5. Accomplishments • Google code as a communication mechanism

  6. Accomplishments • Create the first WSR and submit it • Test some functionalities of Google code • Create a banner for the team logo • Red flags and issues: NONE • Next meeting: Sept. 3rd, 2008, 5.40pm, SL116

  7. To Do List • Select a Software Developer Tool. • Select a Programming Language based on the team members experience.

  8. Questions?

More Related