Please enable JavaScript.
Coggle requires JavaScript to display documents.
The E-Card System Breakdown (Evidence Checklist (Not in Order) (Project…
The E-Card System Breakdown
Key Project Aspects
Project Timescale
Project Plan
Define Client Requirements
processes of system
time scales and milestones - project plan
inputs and outputs of system
risks and constraints
The scope and boundaries of proposed system
recommendations for future action
Evaluate factors of success and failure of e-card system in regards to: Risks, Cost and Time Constraints, Staff Skills and Maintenance, Management and User involvement
Things to Create:
Risk Table
Constraints list
Issues Log
Communication Plan between client, us, workers
Most Appropriate Methodology to use for system
Scrum
Flexible, allows for set tasks to be completed within timescales
Prototyping
Allows for user involvement, can be improved through end user feedback
RAD (Other version of Prototyping, i think)
Similar purpose and reasoning as prototyping
DSDM
Utilises timeboxing, MoSCoW rules, prototyping all before the overall development of the project
Least Appropriate Methodology to use
"The benefits of water" Daniel Woodland (Waterfall)
Would take too long to complete within given timescale
One of the slower methods
Evaluate the Computing and Business needs of Cartes de Mode
Organisation Services, Aims and Goals of Organisation, Customer needs, Expectations, Delivery of Cards, Staff needs, Location of staff, premises, customers
What do customers expect / need?
What does Cartes de Mode offer as a service?
How will cards be delivered?
What are the aims and goals of Cartes de Mode?
What staff needs are we required to accommodate to?
Where are the staff located (Remote working? an office?) ?
Email should be sent to Mia Notte for meeting request about the quality of system and suitability against requirements
System Requirements
Social Media Links
Responsive designs for desktop and mobile
Send automatic reminders about events, 3 days beforehand
Send e-cards from the desktop
Quick access view to address book
Receive a receipt to confirm the card
Quick view access to events and reminders
Access to payment facilities
Requires PCI Compliance
Create a diary to record events (calendar basically)
Secure Login
GDPR Compliance
Assignment Structure
Unit Criteria
P3 - Produce a requirement specification to meet the business and computing requirements of an identified organisation
P4 - Produce a design for a computing system that will meet the business and computing requirements of an identified organisation
P5 - Explain how feedback has been used to refine the design for a computing system that will meet the business and computing requirements of an identified organisation
M2 - Justify the decisions made in a requirement specification to meet the business and computing requirements of an identified organisation
M3 - Justify system design decisions made, showing how the proposed computing system will meet the business and computing requirements of an identified organisation
D2 - Evaluate the requirements specification and design against the organisation's requirements
D3 - Demonstrate individual responsibility, creativity and effective self-management in producing a design for a computing system
Evidence Checklist (Not in Order)
Project Timescale
Record of the investigation techniques
Skills Evaluation
Computing and business needs analysis
Specification and Design Evaluation
Risk Assessment
Test Plan and schedules
Requirements specification
Design Documentation
Record of meetings
Requirements Specification Evaluation
Questionnaire