Suggestions for Week 2

Some things that good team presentations included:

PowerPoint Made the PowerPoint look very nice Included lots of images Put in a lot of text explaining what they are doing

Read the Spec carefully Understood what the spec says Looked up words they didn’t understand Identified what functional features are mentioned in the spec Identified what types of users are mentioned in the spec Identified what technologies are mentioned in the spec

The Team:

Consider team tools Considered any of the following: Creating a FACEBOOK GROUP Setting up a GOOGLE DRIVE Setting up a shared DROPBOX Setting up GITHUB Creating a TRELLO instance Setting up a ONENOTE instance

Roles When assigning roles, remembered that it is not that the person with that role has to do all the work in that area, everyone in the team must contribute to each of the roles, but the person who is named in a particular role is the one who has final sign-off in that area. Had a slide for each member and a bit of text on why they are suitable for their role.

Requirements Gathering:

Investigating Similar Applications Looked for a few different examples. Not just looking at the homepage, looking at the pages within Highlighting what is good about the application, and what can be used as inspiration Looking at what they though wasn’t good about the application, and looking at ways they could improve on it.

End-Users Identified people who use similar software systems, and will speak to them face-to-face or by e-mail Will use Wizard-of-Oz prototyping to get user requirements Discussed issues with lab tutor Considered user satisfaction

Planning:

Plan Had a clear plan. Divided it into clear stages Provided detail on each stage

Milestones Created a timeline: WEEK 5 WEEK 1 WEEK 3 WEEK 7 WEEK 6 We will be looking at… WEEK 1 We will be looking at… WEEK 3 We will be looking at… WEEK 7 We will be looking at… WEEK 6 We will be looking at… WEEK 2 We will be looking at… WEEK 4 We will be looking at… WEEK 8 We will be looking at…

System Development:

Software Methodology Selected a methodology that suits the team: Test-Driven Development Feature-Driven Development User-Centred Development Agile XP SCRUM DSDM

Technical Architecture Included a technical architecture diagram:

Interface Considerations Good groups considered: Universal Design Usability Accessibility Friendly Portability Configurable Minimum number of clicks

Technical Design Looked at the possible use of the MVC Looked at the possible use of Design patterns Included a Use Case for each type of user they though will be using the system

Functional Design Good groups considered: What is the overall goal of the application? What will the application do? Who will be using it? How do we handle errors? What additional features will be added that are not in the spec?

Database Schema Good groups considered: Can we create an initial schema? What is the key data to be stored? How do different elements of the data relate to each other?

Security Considerations Good groups considered: Are we doing security testing? Is their data confidentiality considerations? How are we going to deal with the payments elements of the application (if applicable)? Are we protecting against SQL injection?

Testing Considered looking at a formal testing framework: JUnit, CUnit, TestApe, Unity, JMock, JTest, PowerMock, Unitils, QUnit, Unit.js, Jasmine, PHPUnit Looked at static and dynamic testing Developed test plans

Provide a good summary WHAT WE KNOW WHAT WE DON’T KNOW A range of different languages What project we are doing They we will all code What programming environment we are using What programming language we are using WHAT WE DON’T KNOW Each other’s skills A full functional specification A clear test plan What the security consideration are What are secondary and what are primary features