-
Notifications
You must be signed in to change notification settings - Fork 0
Iteration 1
- Design aesthetically pleasing UI for the app to create a seamless user experience. This was done is 3 stages, see User Interface Prototype page.
- Complete functionality listed in Scope of Software Requirements Specification and Main Product Features & Capabilities of Software Design Specification pages.
| Allocation | Role | Description |
|---|---|---|
| Harry G | Manager, System architect, Programmer, Configuration control | Chiefly responsible for the project schedule and project plan and how progress compares to the plan. Responsibility is understanding and communicating the system requirements.The programmer is responsible for turning the need for system capabilities into something a computer with actually run. |
| Harry H | User Interface, Quality control | Usability expert who takes usability into consideration. Responsible for ensuring that usability decisions are not overlooked. Ensures that quality goals are being met. |
| Sunny | System architect, Technical documentation, Programmer | Responsibility is understanding and communicating the system requirements. Documentation written for developers and maintainers of a system. The programmer is responsible for turning the need for system capabilities into something a computer with actually run. |
| Robert | Database, System architect | Responsibility is understanding and communicating the system requirements. |
| Jesse | Icon designer, User interface | Usability expert who takes usability into consideration. Responsible for ensuring that usability decisions are not overlooked.Responsibility is design the icon. |
| Tori | User documentation, Requirements analyst | Creates documentation for the users of the software system. Understanding and communication the system requirements. Identifies the stakeholders, eliciting requirements, establishing priorities and documenting progress. |
- See Issues in SRS Review Summary page.
- See the Development Pipeline page for a list of issues created as the project progresses.
| Task | Hours |
|---|---|
| Logo Design | 2 |
| Documentation | 6 |
| UI Design | 10 |
| DB Config Swapping | 10 |
| Programming | 10 |
| Test | 10 |
See User Interface Prototype page.
- Software Requirements Specification
- Software Design Specification
- Test Plan
- Team & Roles
- User Manual
See Meeting Summaries page.
| Keep | Try | Problem |
|---|---|---|
| Working well as a team | Buirlding the actual app | Setting up porject structure |
| No conflict | Design what the app looks like | Distractions |
| Everyone contributing | Coding functionality | Equal work load across the board |
| Rate of progression | Try the KAIZEN development process | |
| Team member roles | Exploring the skills and talents of each individual | |
| Communication between the team |
See Process methods and tools page.
For the next iteraction of CTrack, it is planned that the app will include more functionality. These will include:
- More activity tracking, e.g. linking water, electricity and public transportation usage accounts if privacy permitts.
- The option to expand one's garden with more in-app puchases from points calculated from activities.
- THe option for users to have premium accounts which allows them to view better environmental articles, pay real buy to obtain high-tier garden plans, and have personalised tracking activities.
It is also planned that CTrack would be further developed to be used by businesses so they can strive to reduce their environmental impact and become greener. This is a good way foward considering there is a large market for more environmentally friendly businesses in China (this will be later discusses in the business planning).
Futhermore, due to time constraints stage 3 UI was unable to be implemented in every page of the app; hence it is aimed that for the next interation, the modern UI in stage 3 would be integrated throught the whole app to creating a better user experience.