Expectations for the Week & the Software Development Lifecycle JAMS Workshop Makerere University September 2010.

Slides:



Advertisements
Similar presentations
Course: e-Governance Project Lifecycle Day 1
Advertisements

<<replace with Customer Logo>>
Sixth Hour Lecture 10:30 – 11:20 am, September 9 Framework for a Software Management Process – Artifacts of the Process (Part II, Chapter 6 of Royce’ book)
GAI Proprietary Information
Static Structure: Process Description
A sample Service Oriented Architecture for Integrating Government Lines of Business.
Stepan Potiyenko ISS Sr.SW Developer.
SE 470 Software Development Processes James Nowotarski 21 April 2003.
Lesson-12 Information System Development-2
CATEGORIES OF INFORMATION There are three main categories of business information,and these are related to the purpose for which the information is utilized.
SE 555 Software Requirements & Specification Requirements Management.
IS 421 Information Systems Management James Nowotarski 16 September 2002.
Irwin/McGraw-Hill Copyright © 2000 The McGraw-Hill Companies. All Rights reserved Whitten Bentley DittmanSYSTEMS ANALYSIS AND DESIGN METHODS5th Edition.
Database Administration
CS350/550 Software Engineering Lecture 1. Class Work The main part of the class is a practical software engineering project, in teams of 3-5 people There.
SwE 313 Introduction to Rational Unified Process (RUP)
Wael Ellithy, Ph.D. Arx ICT  Agile Software Development  Scrum Framework  Scrum Rules and Process  Scrum In Industry.
Supervisor: Mr. Huynh Anh Dung Students: To Quang Duy Pham Ngoc Tien Nguyen Luong Ngoc Chau Nguyen Hoang Phuc Nguyen Thi Trang.
Software Documentation Written By: Ian Sommerville Presentation By: Stephen Lopez-Couto.
Supervisor: Mr. Huynh Anh Dung Students: To Quang Duy Pham Ngoc Tien Nguyen Luong Ngoc Chau Nguyen Hoang Phuc Nguyen Thi Trang.
ITPD PRODUCTION SUPPORT PROCESS OCTOBER 8, /15/2015 Guiding Principles 1.Support the business area’s needs to execute transactions and expand.
> Blueprint Kickoff >. Introductions Customer Vision & Success Criteria Apigee Accelerator Overview Blueprint Schedule Roles & Responsibilities Communications.
Configuration Management Process and Environment MACS Review 1 February 5th, 2010 Roland Moser PR a-RMO, February 5 th, 2010 R. Moser 1 R. Gutleber.
Process: A Generic View n A software process  is a roadmap to building high quality software products.  provides a framework for managing activities.
Introduction to Project Management
T Software Development Project I Customer Info Jari Vanhanen Ohjelmistoliiketoiminnan ja –tuotannon laboratorio Software Business and.
BTS730 Communications Management Chapter 10, Information Technology Management, 5ed.
Software Configuration Management
Thirteenth Lecture Hour 8:30 – 9:20 am, Sunday, September 16 Software Management Disciplines Process Automation (from Part III, Chapter 12 of Royce’ book)
Commonwealth of Massachusetts Statewide Strategic IT Consolidation (ITC) Initiative ANF IT Consolidation Website Publishing / IA Working Group Kickoff.
T Software Development Project I Customer Info Jari Vanhanen Ohjelmistoliiketoiminnan ja –tuotannon laboratorio Software Business and.
Software Engineering Project: Research Expert Prabhavathi Kumarasamy Joshua Thompson Paul Varcholik University of Central Florida.
Requirements Verification & Validation Requirements Engineering & Project Management.
Teaching an Object-Oriented Software Development Lifecycle in Undergraduate Software Engineering Education February 27, 2002 Professor Brian Blake Georgetown.
© 2012 Cengage Learning. All Rights Reserved. This edition is intended for use outside of the U.S. only, with content that may be different from the U.S.
ICT Standards and Guidelines The Structure of the Project Akram Najjar CNSI – Senior Consultant Director of InfoConsult.
Sampleminded® Support Overview Last Updated: 1/22/
Introduction Complex and large SW. SW crises Expensive HW. Custom SW. Batch execution Structured programming Product SW.
Software Quality Assurance
ITPD PRODUCTION SUPPORT PROCESS OCTOBER 8, /23/2015 Guiding Principles 1.Resolve production issues in a timely and effective manner 2.Manage.
T Project Review WellIT PP Iteration
SMAP 5 - Kickoff 19 March IBM Smarter Planet Agenda Introductions Background (SMAP) Proposed Component Model General discussion on approach An overview.
STAKEHOLDER MEETING Selecting Interventions to Improve Utilization of the IUD City, Country Date Insert MOH logoInsert Project logoInsert USAID logo (Note:
BSBPMG501A Manage Project Integrative Processes Manage Project Integrative Processes Project Integration Processes – Part 1 Diploma of Project Management.
Yazd University, Electrical and Computer Engineering Department Course Title: Advanced Software Engineering By: Mohammad Ali Zare Chahooki The Rational.
Using Open Source Projects in Higher Education: A Two-Way Certification Framework Pantelis M. Papadopoulos, United Nations University Ioannis G. Stamelos,
European Middleware Initiative (EMI) The Software Engineering Model Alberto Di Meglio (CERN) Interim Project Director.
ESSRT In-Process Review September 10, Agenda 1.Work Completed Till Date 2.Scope of future activities and deliverables 2.
Supervisor: Mr. Huynh Anh Dung Students: To Quang Duy Pham Ngoc Tien Nguyen Luong Ngoc Chau Nguyen Hoang Phuc Nguyen Thi Trang.
T Iteration Demo Tikkaajat [PP] Iteration
Week 7 Lecture Part 2 Introduction to Database Administration Samuel S. ConnSamuel S. Conn, Asst Professor.
Irwin/McGraw-Hill Copyright © 2000 The McGraw-Hill Companies. All Rights reserved Whitten Bentley DittmanSYSTEMS ANALYSIS AND DESIGN METHODS5th Edition.
Arend-Jan Speksnijder Solutions Architect Microsoft Dynamics Lighthouse team Dynamics AX2009 Technical Overview and Demo (DYN301)
The Software Engineering Process Discussion Slides.
David M. Kroenke and David J. Auer Database Processing Fundamentals, Design, and Implementation Appendix B: Getting Started in Systems Analysis and Design.
Introduction to Software Engineering Muhammad Nasir Agile Software Development(2)
Internal developer tools and bug tracking Arabic / Hebrew Windows 3.1Win95 Japanese Word, OneNote, Outlook
Software Engineering Process - II 7.1 Unit 7: Quality Management Software Engineering Process - II.
T Iteration Demo LicenseChecker I2 Iteration
Chapter 2- Software Development Process  Product Components  Software Project Staff  Software Development Lifecycle Models.
From manual test shop to fully automated test coverage: A How-To session to speed up your journey Jayshree Bhakta ITHAKA/JSTOR.
Office 365 Security Assessment Workshop
Wael Ellithy, Ph.D. Arx ICT
1.Introduction to Rational Unified Process (RUP)
Software Documentation
CPMGT 300 Competitive Success/snaptutorial.com
CPMGT 300 Education for Service/snaptutorial.com.
Quality Assurance in an Agile Development Team Michelle Wu 2018 PNSQC
Enterprise Program Management Office
Presentation transcript:

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 MondayTuesdayWednesdayThursdayFriday 9:00 Expectations for the Week, Software Lifecycle Project Management AppLab & Community Knowledge Worker Group Work SessionHoliday 9:30 10:00 Writing Functional Specifications Group Work Session 10:30 11:00 Test-Driven Development 11:30 12:00 Object-Oriented Design 12:30 1:00 Lunch Break 1:30 Facilitator Office Hours 2:00 Introduction to the group activity 2:30 3:00 Initial group work session: setup, assign roles, start working 3:30 4:00 4:30 5:00 Team Presentations (15 x 8 min each) Awards 5:30 6:00 6:30 7:00 8:00

Schedule v2 MondayTuesdayWednesdayThursdayFriday 9:00 Expectations for the Week, Software Lifecycle Project Management AppLab & Community Knowledge Worker Holiday / Facilitator Office Hours Team Presentations (15 x 8 min each) Awards 9:30 10:00 Writing Functional Specifications Group Work Session 10:30 11:00 Test-Driven Development 11:30 12:00 Object-Oriented Design 12:30 1:00 Lunch Break 1:30 Facilitator Office Hours 2:00 Introduction to the group activity 2:30 3:00 Initial group work session: setup, assign roles, start working 3:30 4:00 4:30 5:00 5:30

Workshop Materials All materials we use for the workshop are available at – 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 …

Who We Are Kenny Wolf Software Microsoft 8 years on.NET Framework 5 years on Mac Office Plays drums & juggles Lauren Lavoie Program Microsoft 4 years on Exchange 3 years on Windows Presentation Foundation Likes yoga & photography 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

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

Software Development Roles Developer Responsible for designing and implementing features Implements basic test coverage Program Manager Writes functional specifications to bridge between business and technical teams Keeps the engineers unblocked Test Engineer Writes test plans and test cases Implements test cases Advocates for the customer Operations Manager Responsible for deploying and monitoring product code Business Stakeholder Provides business requirements Release Manager Drives the project schedule Software Architect Proposes (and sometimes implements) big architectural changes Reviews and advises on design Customer The consumer of the software The most important person

Software Development Lifecycle Gather Requirements Design the System Implement the System Quality Assurance & Documentation Operate & Maintain

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

Source Control 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() 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. "Sync" (i.e. get updates) Merge CalculateScore()

Bug Database

Document Repository

Coming Attractions Gather Requirements Design the System Implement the System Quality Assurance & Documentation Operate & Maintain Session 2: Writing a Functional Spec Session 4: Coding Guidelines & Object- Oriented Design Session 3: Software Testing & Test-Driven Development Session 6: Project Management