Payment Feature PHP Script...

Here's an example of my php code which I will be using as the basis for my final feature later on in the project:

Enter Your Name:


Event Name:

Quantity:

Enter Price:

Testing Feature...

I have started thinking of tests for my feature. I have posted my version on the discussion board to get more ideas from the other group members.

Test Number
Feature/Test Description
Test Data
Expected Outcome
Actual Outcome
Additional Steps Taken
1
Payment Button
Other Features on the page. To Test to see if information is carried across to payments page.
All the information collected from the other features should be transferred across to the payments page.


2
Payment Button
Hyperlink to payment page
Should open the payment page.



Test Number
Feature/Test Description
Test Data
Expected Outcome
Actual Outcome
Additional Steps Taken
1
Payment Button
Other Features on the page. To Test to see if information is carried across to payments page.
All the information collected from the other features should be transferred across to the payments page.


2
Payment Button
Hyperlink to payment page
Should open the payment page.

To see the tabled layout, see the discussion forum.

Draft Features Spec + Other Issues

Myself, Richard Gibbons and Rob Morrisby are currently putting together the draft copy of the document. It is going OK, however there are certain issues that have crept up. For example people who have not got a feature need allocating one. We have resolved this by splitting up the features, after we have talked with the people it affects. Maybe for the future it might be handy for everyone to know the format, IE text etc for the final copy so that it makes putting together a lot easier. From the lecture today, we also need to add a project plan and testing. I think this can be a separate section on to the current proposal, composing of a few tests for every ones feature. I will be suggesting this on the forum, so that we can implement this for the final copy.

We need to create a project plan composing of who needs to be doing what during the next 3 weeks. I have created a template, and so far everyone has signed up to it. The project plan should be complete within the next couple of days. Included on that same thread is a list of all the features and allocated rooms, which Jennie Bate will be matching names with the features shortly.

I will be creating a separating Testing thread, which could work in the same way as with the feature documentation, it should be straight forward then.

For my demo on Thursday, I have produced a prototype of how my feature may work, it should be enough for me to get feedback on and shows how it interacts with other features.

One final note is that a lot of the people have not resubmitted their improved feature so we have decided to just submit the one they submitted originally. I have posted a lot of threads on the discussion forum, the majority of people replied how ever a few didn't.

Systems Integration...

I will be creating a new thread, with these questions that need to be considered:

What Hardware do we need?
What Software?
How long will it take?
Deadlines?
What facilities are available?

The above questions are just a starting point, but we need suitable ideas for the demonstration next week.

Proceed to Payment Feature...2

With every ones feature may only require a certain amount of coding, it is still important to decide on how to do it and also how it will link with the other features for the system. My designs have stated that it will gather all the information collected by the features on the same web page as mine and pass it on to the payment section.

In terms of the demo next week, I may just decide to talk through what I will want to achieve with my feature, rather than just demonstrating pushing the button. As well as the link to the payments page, there will be a lot of php coding which will include the use of sessions and other functions available.

Current Update of SB2

With our last meeting held on Tuesday. SB2 has taken another major turning point. The way we have to work and meet deadlines has changed considerably. As well the design and implementation of our individual features, we now have to consider other roles to take on in order to make this project a success. This roles will include Design of the database, IE layout, Systems Integration, Database Structure, Testing and Marketing and Finance.

I will be helping to get our cohort's final proposal put together in the next week, as a representative for Consortium B. In terms of the new roles I will be part of the group that helps with the System Integration.

For the demonstration next week, we need to decide on what we want to achieve at that stage of the product, again this will need to be discussed on the discussion boards first. Also I presenting my feature to which is the proceed to payment button.

Cohort Spec...

As a Cohort we have to produce a series of diagrams and models to show our system. I have proposed the following on the discussion board:

As a cohort we need to get these things done, Any volenteers?

Web design – site maps/menu maps – the structure of the website.

Style Guide - colours, fonts, button shapes, text size, page layout etc etc.

Storyboards/wireframes.

Use Case models (with Use case descriptions) can provide information about the functions of the system.

Entity relationship model to help to design the database.

Requirements Catalogue to provide a list of prioritised requirements.


Point B needs to be decided on quickly so that the whole cohort knows how to redesign their features.

We could split this up between the 3 consortiums again, Or have 6 different threads for the points above so everyone can get involved and add their own ideas. What does everyone think?