Software Development/Improvement Project
Timeline
-
November 10, 2020Experience start
-
November 12, 2020Concept Note Development
-
November 14, 2020Project Charter
-
November 22, 2020Project Plan
-
November 29, 2020Software Requirements Specification Document
-
December 13, 2020Design Specification Document
-
February 14, 2021Experience end
Timeline
-
November 10, 2020Experience start
-
November 12, 2020Concept Note Development
Meeting between students and company to confirm: project scope, communication styles, and important dates.
-
November 14, 2020Project Charter
Upon approval of the concept note, your team will move towards drafting the project charter with the outline provided in the Assessment Brief.
-
November 22, 2020Project Plan
A plan of the stages, activities and tasks in the project, providing explanation where necessary - should include work breakdown structures, detailed task lists and Gantt charts
-
November 29, 2020Software Requirements Specification Document
A document containing business, user, system requirements that describes what the software will do and how it will be expected to perform.
-
December 13, 2020Design Specification Document
A document that focuses on how the system will be constructed. It should contain data design, architectural design, interface design and component-level design.
-
January 17, 2021Prototypical Development Solution
Software project files with supporting write-up on the team’s approach to systems implementation (agile vs waterfall-based approach), risk management and quality assurance.
-
January 24, 2021Deployment Plan
A detailed document that considers the people, processes and technology that need to be in place for the system to be successfully installed, adopted by the user community, and the benefits of the system to be realized.
-
January 24, 2021Test Plan
A detailed document that describes the test strategy, test cases, schedule, and resources required to perform testing for a software solution.
-
February 1, 2021Video Presentation to Client
A video presentation of a working prototypical solution, the plan for testing test plan and deployment strategy
-
February 1, 2021Video Presentation to Client
A video presentation of a working prototypical solution, the plan for testing test plan and deployment strategy
-
February 1, 2021Video Presentation to Client
A video presentation of a working prototypical solution, the plan for testing test plan and deployment strategy
-
February 14, 2021Experience end
Experience scope
Categories
Information technology Operations Project managementSkills
software development requirements engineering business consulting project management systems analysis and designThe purpose of this project is to provide students with an opportunity to apply and develop the necessary soft skills of leadership, professionalism and adaptability required by the real-world work environment. Students will use these hard and soft skills to devise and execute a systems development plan or system improvement plan which will entail requirements engineering, software development, and project management towards the development and implementation of a functional software system for an organization.
Learners
- Concept Note - a brief outline of the project you have in your mind.
- Project Charter– a document which describes the purpose of a project and its scope and legally authorizes the beginning of the project
- Project Plan- based upon the charter, provide a plan for the stages, activities and tasks in the project
- Software Requirements Specification– a document containing business, user, system requirements that describes what the software will do and how it will be expected to perform.
- Design Specification Document– a document that focuses on how the system will be constructed i.e. data, architectural, interface and component-level designs.
- Prototypical solution– software project files
- Test Plan– a document that describes the test strategy, test cases, schedule, and resources required to perform testing for a software product.
- Deployment Plan– a document that considers the people, processes and technology that need to be in place for the system to be successfully installed and accepted
Project timeline
-
November 10, 2020Experience start
-
November 12, 2020Concept Note Development
-
November 14, 2020Project Charter
-
November 22, 2020Project Plan
-
November 29, 2020Software Requirements Specification Document
-
December 13, 2020Design Specification Document
-
February 14, 2021Experience end
Timeline
-
November 10, 2020Experience start
-
November 12, 2020Concept Note Development
Meeting between students and company to confirm: project scope, communication styles, and important dates.
-
November 14, 2020Project Charter
Upon approval of the concept note, your team will move towards drafting the project charter with the outline provided in the Assessment Brief.
-
November 22, 2020Project Plan
A plan of the stages, activities and tasks in the project, providing explanation where necessary - should include work breakdown structures, detailed task lists and Gantt charts
-
November 29, 2020Software Requirements Specification Document
A document containing business, user, system requirements that describes what the software will do and how it will be expected to perform.
-
December 13, 2020Design Specification Document
A document that focuses on how the system will be constructed. It should contain data design, architectural design, interface design and component-level design.
-
January 17, 2021Prototypical Development Solution
Software project files with supporting write-up on the team’s approach to systems implementation (agile vs waterfall-based approach), risk management and quality assurance.
-
January 24, 2021Deployment Plan
A detailed document that considers the people, processes and technology that need to be in place for the system to be successfully installed, adopted by the user community, and the benefits of the system to be realized.
-
January 24, 2021Test Plan
A detailed document that describes the test strategy, test cases, schedule, and resources required to perform testing for a software solution.
-
February 1, 2021Video Presentation to Client
A video presentation of a working prototypical solution, the plan for testing test plan and deployment strategy
-
February 1, 2021Video Presentation to Client
A video presentation of a working prototypical solution, the plan for testing test plan and deployment strategy
-
February 1, 2021Video Presentation to Client
A video presentation of a working prototypical solution, the plan for testing test plan and deployment strategy
-
February 14, 2021Experience end
Project Examples
Requirements
In the past, students would have embarked on various types of software development projects. A small list of such projects is shown below:
- Television and Radio Booking Management Systems
- Inventory Management Systems
- Single Window Automated Processing System (SWAPS)
- A Research Dissemination Platform for Universities
Additional company criteria
Companies must answer the following questions to submit a match request to this experience:
Be available for a quick phone call with the instructor to initiate your relationship and confirm your scope is an appropriate fit for the course.
Provide a dedicated contact who is available to answer periodic emails or phone calls over the duration of the project to address students' questions.
Be available to approve project documents depending on the software development approach taken by the students
Timeline
-
November 10, 2020Experience start
-
November 12, 2020Concept Note Development
-
November 14, 2020Project Charter
-
November 22, 2020Project Plan
-
November 29, 2020Software Requirements Specification Document
-
December 13, 2020Design Specification Document
-
February 14, 2021Experience end
Timeline
-
November 10, 2020Experience start
-
November 12, 2020Concept Note Development
Meeting between students and company to confirm: project scope, communication styles, and important dates.
-
November 14, 2020Project Charter
Upon approval of the concept note, your team will move towards drafting the project charter with the outline provided in the Assessment Brief.
-
November 22, 2020Project Plan
A plan of the stages, activities and tasks in the project, providing explanation where necessary - should include work breakdown structures, detailed task lists and Gantt charts
-
November 29, 2020Software Requirements Specification Document
A document containing business, user, system requirements that describes what the software will do and how it will be expected to perform.
-
December 13, 2020Design Specification Document
A document that focuses on how the system will be constructed. It should contain data design, architectural design, interface design and component-level design.
-
January 17, 2021Prototypical Development Solution
Software project files with supporting write-up on the team’s approach to systems implementation (agile vs waterfall-based approach), risk management and quality assurance.
-
January 24, 2021Deployment Plan
A detailed document that considers the people, processes and technology that need to be in place for the system to be successfully installed, adopted by the user community, and the benefits of the system to be realized.
-
January 24, 2021Test Plan
A detailed document that describes the test strategy, test cases, schedule, and resources required to perform testing for a software solution.
-
February 1, 2021Video Presentation to Client
A video presentation of a working prototypical solution, the plan for testing test plan and deployment strategy
-
February 1, 2021Video Presentation to Client
A video presentation of a working prototypical solution, the plan for testing test plan and deployment strategy
-
February 1, 2021Video Presentation to Client
A video presentation of a working prototypical solution, the plan for testing test plan and deployment strategy
-
February 14, 2021Experience end