User / Member a case in the case tracking system
- The set the category of case they believe it to be one of the following
- Bug
- Feature Request
- Report Required
- Change Request
- They set the case status to open
- They provide Detailed information including where appropriate including : Browser in use, Screenshot, Error messages
The project co-ordinatorthen reviews the case.
- Verify sufficient information has been provided
- Verify Categorisation of the case
- Verify that the request is within original requirements specification against specification document and give specification reference.
- If its not within the original scope then they will either close the case or provide budget authorisation and codes if the work is to go ahead.
- They Set the priority of the work and set the required date / Release version its targetted for.
- For all case categories except "Bug" They assign the case to a business analyst,
- Bugs are assigned directly to the Development team to assess / Fix
Business analyst then :
- Develop's business specification from requirements and insert requirements / reference into the case,
- The requirements must include all test cases that are to be used for veification of successful complete.
- Where require they also develop the Brief for designers, brief the content developers of any required content and brief the trainers on the training materials needed.
- They brief the UAT and requirements testing team(s) They then create the work cases and assign the work to the teams, the teams below have to work in an itterative and co-ordinated manner dependant on the type of work required.
- The Project co-ordinator is responsible for co-ordination between the teams.
| Designer(s) |
Content Team
|
Development Team
|
Testing Team
|
| Designers then Develop Layouts, Grids and photoshop images and provide to Development team |
Develop the required content.
|
The development team then complete Solution design. |
Develop Testing Plan
|
| Develop UI requirements / specification to provide to Development team |
Publish Content
|
They provide time Estimate time. |
|
| Provide Icons, images and other required artworks to development team |
|
Implement Fuctionality and do the Unit testing |
|
|
|
|
Implement the functionality |
|
Bookmark/Search this post with:
About the procedure to go on and conclude this testing period
First of all, thanks a lot Rory for your suggestion. Your procedure is perfect for D2.2. "Build solution and test" as -as I understand it- documents the way you test the solutions you develop. In fact, if this is a kind of summary of a more extense methodology, in my opinion, you should report the whole methodology to the European Commission to present that a structured set of procedures have been used at the corresponding stage of the project. This on one hand. On the other hand, the thing is that at this stage I don't think is realistic to do it like that. The role of coordination of Atos does not allow us to decide which changes/suggestions should be fulfiled or not. This revision process is something all the partners should do as all of them need to validate the final site that will be opened to external users. Being all of us in time would allow us to give a structured procedure to these last days feedback. But this task ought to be finalised at month 4 and we are at month 8 and need to keep this task in more practical grounds. My suggestion, if you all agree is:
1. Bugs need to be fixed and this need no external revision or agreement: the site needs to work without errors and bug fixing is a mandatory task along the life of the project.
2. Suggestions to improve the site or proposals of new features. With this respect I have to say that your work is impressive and I really thank you and Fintan for being so fast and flexible. In my opinion, all suggestions should be agreed by everybody, but for practical reasons I would say that:
2.1 suggestions from one partner that are given no negative feedback by other partners (in general all things said to date have been sensible and have rised no controversy or amendment) and are reasonably easy to solve, please, I kindly ask you to solve them. Document all the requests and the solutions given by you in D2.2 and in the report to justify efforts and claim costs to the EC.
2.2 suggestions that might rise a discussion would be listed and discussed among partners before deciding what to do with them. Again if those are agreed by the consortium and easy to implement, I also ask you to, please, develop them.
2.3 finally, those suggestions agreed by everybody (or at least not disagreed by any partner) that might imply an extra cost, should be also listed apart to take a decision on them.
Of course we should follow a short calendar for all these actions. My suggestion is that we go on with our internal testings until the 28th of September. 21st and 28th (Fridays) will be used to review those previously mentioned lists of suggestions that need to be discussed. Decisions will be taken eventually in the corresponding telcos. By the fist of October, all the revision would have concluded and eCademy will have time to finalise with the pending changes on the site (deadlines will be discussed if necessary at the light of the pending tasks). I'm reviewing the state of deliverables produced to date and come back to you with this major issue on Monday.
Thanks a lot to all of you for your active responsiveness this week.
Yoram, I think you should
Yoram, I think you should put these suggestion on the Spidera Support Group Forum (as here few people have subscribed) in order to have a debate and a consensus on the things to amend/improve.
...also because they are all very good suggestions !!
Andrea
suggestions
guys, after some use of the platform I find it really promising.
Few comments/suggestions:
1. sometime to time I get error screens from MYSQL. this is usually solved in a snap by refreshing the browser. Still, if this can be investigated further - even better. Is that possible that you need to put a small delay (~1 sec) before connecting to the DB engine so it can "reset" properly? just a wild idea...
2. Need to consider the texts you provide with automated notifications and use them wisely. First I think these should be short. However sentences like "enjoy your new freedom" are nice but I doubt if these are good for the LSH community ;-) I rather add short tips for the users like "did you know you can do .... by clicking ..." etc.
3. Maybe use the automatic notifications to suggest people to "enhance their membership" e.g. complete profiles, link to other people, invite new people, post blogs etc. It needs a rather smart engine and I'm not sure if your templates can handle it.
4. Need to design the process of greeting and treating new member that joined resulting from invitation in terms of providing exact guidance because I estimate that most users will not have a clue what they're suppose to do when they login first time.
5. Alternatively, maybe like LinkedIn, once in a while (bi-weekly?) go over the list of subscribers, find out where they lack (missing/incomplete profiles, low # of contacts, ...) and motivate them to do it via message with link.
6. You can use Dunja's expertise to make searches for people that are not in the platform and match them with members and suggest these members to invite these external people. This is a strong feature that no other platform is capable to do.
So far.
YLY