Well done everyone,
Its done and dusted and handed in.
Cake and ice cream for everyone :D
Requirements Engineering
Our Project for Requirements Engineering Members: Peter Fleming, Kevin Moynihan, Jason O'Sullivan, Hugh Desmond
Monday, December 6, 2010
Thursday, November 18, 2010
Moving swiftly on..
Hey everyone,
As we are already aware we've handed the elicitation techniques report to Mary.
So next stage is to get a move on with getting the actual project.
Things we need to do..:
Create a glossary
The goal of the glossary is to provide a common vocabulary on which all of the stakeholders agree. The glossary defines all the meaning of the terms relevant to the system being built. These serve as the foundation for all requirements models and business rules.
Create a Business Rules Document
Business rules or business rules sets describe the operations, definitions and constraintsthat apply to an organization to achieving its goals.
Create a prototype of the proposed system
This should be used to illustrate all main usage scenarios.
As we are already aware we've handed the elicitation techniques report to Mary.
So next stage is to get a move on with getting the actual project.
Things we need to do..:
Create a glossary
The goal of the glossary is to provide a common vocabulary on which all of the stakeholders agree. The glossary defines all the meaning of the terms relevant to the system being built. These serve as the foundation for all requirements models and business rules.
Create a Business Rules Document
Business rules or business rules sets describe the operations, definitions and constraintsthat apply to an organization to achieving its goals.
Create a prototype of the proposed system
This should be used to illustrate all main usage scenarios.
Create Use Case Diagram
This is used to illustrate functional requirements.
Create a data Dictionary
For each entity list the attributes of that entity and for each attribute give the following information
- Attribute name
- Attribute description
- Attribute data type, i.e number, text, etc
- Attribute Nullability, i.e. wether the attribute is required or optional
- Attribute default, i.e. the default value for the attribute if applicable
Create a supplementary specification
This is used to document all non functional requirements
We need to save all versions of our work so dont save over something if u got it corrected/checked, save as a new draft.
Tuesday, November 9, 2010
Interview
Hey,
I took the questionnaire that we all came up with and brought it into centra and interviewed this store manager John O'Sullivan.
I met up with him and we went through the questionnaire, there were certain parts that required further explanation, but thats why combining the two processes together was worthwhile..
I gathered documents from the shop which will help us to define business rules for the project..
I got good information about how to produce the various financial reports that our system will be required to generate..
im working on the evaluation and summay at the moment...
I'll see ye in the morning :P
slán :)
Sunday, November 7, 2010
questionnaire first draft
Well...i've come up with a questionnaire which will mainly narrow down the business rules of the company, it's only a rough draft however, which mainly focuses on the delivery section of the proposed new system, i think peter will take elements of the questionnaire to help out with his interview questions but alas it's up to him if he wants to use it or not....if there's anyway ye think i can improve the questionnaire, please don't hesitate to give me a shout...anyway it's one am here so i'm gonna hit the hay and attempt another part of the project tomorrow...don't know what yet but i'll figure something out :D
ps the questionnaire is up on dropbox as i can't figure out how to put it up on the blog here
Thursday, November 4, 2010
questionnaire
i'm now in the process of coming up with questions for the questionnaire that i will set out in order to get the business rules, which will act as the constraints or non-functional requirements for the new online system, the main topics i will include in the questionnaire will be
1) online discounts
2) times that the delivery service will / should be in operation
3) delivery area i.e. 2 / 3 / 4/ 5 mile radius of store
4) printed invoices or receipts
5) methods of payment ie. charging customer accounts / pay by laser / pay upon delivery etc.
6) etc..
any other topics that you think i should include lads, don't hesitate to post a comment or two...
@peter at the weekend man can you get a copy of a delivery receipt / invoice that we can use for our documentation? If i have to order something and have it delivered to your house i will :P
Wednesday, November 3, 2010
Work
I have emailed the documents to mary to review what we have done so far.... I also requested a full description of what must be included in the topic just in case we are missing anything.
Thursday, October 28, 2010
Group Meeting Thurs 28/10
We met up for a group meeting today, we discussed any problems we were having with our assigned work.
We came up with some sample questions to get the ball rolling for the questionnaire.. i will upload them later...
We agreed that each of us should have a draft of our work done for the next meeting which will be on wednesday.. so that we each know we are on the right track..
We came up with some sample questions to get the ball rolling for the questionnaire.. i will upload them later...
We agreed that each of us should have a draft of our work done for the next meeting which will be on wednesday.. so that we each know we are on the right track..
Subscribe to:
Posts (Atom)