1 / 15

Expectations for the Week & the Software Development Lifecycle

Expectations for the Week & the Software Development Lifecycle. JAMS Workshop Makerere University September 2010. Agenda. Intro & Workshop Schedule Who We Are Software Development Lifecycle Team Roles Overall Lifecycle Tools & Processes. Schedule v1. Schedule v2. Workshop Materials.

miles
Download Presentation

Expectations for the Week & the Software Development Lifecycle

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. Expectations for the Week & the Software Development Lifecycle JAMS Workshop Makerere University September 2010

  2. Agenda • Intro & Workshop Schedule • Who We Are • Software Development Lifecycle • Team Roles • Overall Lifecycle • Tools & Processes

  3. Schedule v1

  4. Schedule v2

  5. Workshop Materials • All materials we use for the workshop are available at http://lawolf.net/jams • PowerPoint slides • Templates (test plan, functional spec, team presentation) • Attendee packet (schedule, project description & evaluation criteria, sample functional spec, sample test plan) • All assignments may be submitted via …

  6. Who We Are Kenny Wolf Lauren Lavoie Program Manager @ Microsoft 4 years on Exchange 3 years on Windows Presentation Foundation Likes yoga & photography • Software Architect @ Microsoft • 8 years on .NET Framework • 5 years on Mac Office • Plays drums & juggles • Finishing a year-long sabbatical volunteering on tech projects in Asia and Africa • Spent the summer volunteering for Grameen Foundation in Kampala, on the Community Knowledge Worker project

  7. Goals for the Week • Provide insight into how software engineering works in industry • Hands-on experience with practical elements of software engineering • Functional specifications • Software testing • Coding as a team • Have fun

  8. Software Development Roles

  9. Software Development Lifecycle

  10. Software as a Team • More people can get more done but… • Can introduce extra dependencies • Require more communication overhead • Can duplicate each other’s work • Can build incompatible pieces • Certain tools and techniques can help • Source control • Bug database • Scheduling tool • Document repository • Project management

  11. Source Control A source control system manages changes to text and binary files. Changes are identified by a "revision number“, and associated with a timestamp and the person making the change. Revisions can be compared, restored, and with some types of files, merged. • Critical for code stability and maintenance • Allows developers to collaborate • If necessary, allows the system to “rollback” to an earlier date • Verbs: Edit, Sync, Submit Source Control System Submit CalculateScore() Merge CalculateScore() Submit CalculateScore() "Sync" (i.e. get updates)

  12. Bug Database Bug Database

  13. Document Repository

  14. Coming Attractions Session 6: Project Management Session 2: Writing a Functional Spec Session 4: Coding Guidelines & Object-Oriented Design Session 3: Software Testing & Test-Driven Development

More Related