PORTFOLIO EVIDENCE FROM TASKS¶
This Icon describes the type of content that could go into the portfolio for the aspect
Activity A(i)¶
- Research notes
Portfolio Content
Explain that the research has been completed.
Inform the reader that the research outcomes are in APPENDIX A.
SEQUENCE 01
Activity A(ii)¶
- Business context
- based on the research completed in Task a(i)
Portfolio Content
DESCRIBE of the context the organisation operates in.
SEQUENCE 02
- Purpose of requirements
- Reasons for creating requirements
Portfolio Content
EXPLAIN why requirements matter to the Project SEQUENCE 03
- Functional requirements
- A list of what the process must do
Portfolio Content
CREATE a list of Functional Requirements.
SEQUENCE 04
- Non-functional requirements
- A list of how the user will experience the app and how it will perform.
Portfolio Content
CREATE a list of Non-Functional Requirements.
SEQUENCE 05
- User analysis
- Problem statements and User Stories
- Empathy analysis
Portfolio Content
- Explain why User Analysis is important and the value to the project
- Mention Design Thinking strategies
SEQUENCE 06
Portfolio Content
You will create Problem Statements, User Stories, and Empathy Analysis
CREATE Problem Statements.
CREATE User Stories.
CREATE Stakeholder Empathy Analysis
SEQUENCE 07
- Decomposition
- Description of Abstraction of main components
Portfolio Content
- DESCRIBE the decomposition process and refer to the Activity B processes for abstraction and algorithm design.
SEQUENCE 08
- KPIs
- What rubric will confirm success
- Two uses: - Value to the project at this stage - Measurable values at Handover
Portfolio Content
CREATE a set of KPIs.
SEQUENCE 09
- Solution description
- The end product
- The technology stack
- The tooling used in development
Portfolio Content
DESCRIBE the proposed solution in detail in terms of the end product, and the tools to be used to create it.
SEQUENCE 10
- Testing strategy
- Alpha tests
- Beta tests
- Release tests
Portfolio Content
DESCRIBE the testing strategy to be used and refer to the testing documentation in Activity B
SEQUENCE 11
- Justifications of meeting needs
- Client needs
- Existing user needs
- Potential user needs
- Development team needs
Portfolio Content
DESCRIBE how the app will meet the needs of the stakeholders listed above.
SEQUENCE 12
- Handover strategies
- KPIs confirmation
- How the solution will be packaged for installation
- How the solution will be delivered or hosted
- Client contract finalisation.
Portfolio Content
DESCRIBE how the final product could be handed ove to the client and made available for to end-users.
DESCRIBE briefly the legal issues of contracts.
SEQUENCE 13
- Support and maintenance proposals
- Bug reporting and resolution
- Feature updates or additions
- Change management
- Legal and Regulatory confirmation.
Portfolio Content
DESCRIBE how the client might be supported after handover
SEQUENCE 14
- Rights Management
- Protocols for rights management
Portfolio Content
DESCRIBE Legal, moral, ethical issues of using media.
DESCRIBE Legal issues for Data Protection
SEQUENCE 15
---¶
Activity B¶
Introduction to ACTIVITY B
PORTFOLIO CONTENT
Write an introduction to Activity B
- Explain the value of good Design Documentation
- Describe the stakeholders who may use it
SEQUENCE 16
- Navigation Diagrams
- A tree diagram illustrating parent - child links
Portfolio Content
CREATE a navigation tree-diagram
SEQUENCE 17
- Decomposition Diagrams
- Modularisation and abstraction
Portfolio Content
CREATE a decomposition diagram based on the Navigation diagram as a starter.
CREATE at least 2 layers of decomposition.
SEQUENCE 18
- UML Diagrams
- Classes
- Data Flow
- Sequence
Portfolio Content
CREATE a UML Class Diagram.
CREATE either a UML Data Flow OR a Sequence Diagram
SEQUENCE 19
- Algorithm definitions
- Pseudocode
- Flowcharts
Portfolio Content
CREATE A Maximum of 5 Diagrams.
Make sure there's a mix of Flowchart and Pseudocode evidence.
SEQUENCE 20
- Database Models
- Conceptual
- Logical
- Physical (MySQL)
- Entity Relationship diagram (ERD)
Portfolio Content
CREATE database models for the scenario.
Suggested: minimum Conceptual and Physical models.
SEQUENCE 21
- Data dictionaries
- Precise definition of data tables
- Precise definition, with examples, of fields in tables
Portfolio Content
CREATE 2 or more Data Dictionaries as tables.
SEQUENCE 22
- UI Design Diagrams
- Wireframe diagrams of pages
Portfolio Content
CREATE Wireframe diagrams for website pages.
- Explain purpose of diagrams
- Explain that lo-fi wireframes are used to validate layout
- Explain that hi-fi layouts will be developed in Task 2 of the project
SEQUENCE 23
- Testing
- Illustration of test sequences
- Record of test item, method of testing, data required, expected outcome
Portfolio Content
CREATE a Test Plan
DESCRIBE the Test Log.
SEQUENCE 24
- Risk Management
- formalised analysis of life-cycle risks
Portfolio Content
CREATE a Risk Register for the development processes
SEQUENCE 25
- Project Review
- How lessons will be learned
- How success will be optimised
Portfolio Content
DESCRIBE how review processes would help all stakeholders.
SEQUENCE 26
- Future developments
- Explanation of how consistency improves development processes
Portfolio Content
Describe potential future enhancements.
Describe team-based development and any issues it raises.
Describe how standardisation of coding styles would aid development.
SEQUENCE 27
-
Task 1 Summary
- Write a summary of the Task 1 activities
- Explain their role in Task 2
-
Portfolio Content
SEQUENCE 28
- APPENDICES
Portfolio Content
- Appendix A Research Notes
- Any other relevant Appendix sections
SEQUENCE 29