Evaluation framework
DECIDE is a framework that is used to guide evaluation
D – Determine the goals the evaluation addresses
E – Explore the specific questions to be answered
C - Choose the evaluation paradigm and techniques to answer the questions.
I - Identify the practical issues.
D - Decide how to deal with the ethical issues.
E - Evaluate, interpret and present the data
1. D – Determine the goals of evaluation
There are four goals of evaluation
a. To understand real world i.e. understand how users employ technology in the real
World and how designs can be improved to fit the work environment better.
b. To enable choose the best alternative of the various designs
c. To enable if the product being made is of the required standards by the users
d. To determine if the target of our project is good enough
2. E – Explore the specific questions to be answered
a. What is the purpose of the product? The purpose of this product is to bring together several bookshops under one site so that it can be easy to search for books and buy the books in the same site
b. Who will be the users/stakeholders? The users will be the customers, the suppliers, the bookshop owners, the advertisers and also the owners of the site.
c. How is it than better than previous interface? The project is better than previous interfaces because we came to capture all the user needs and wants.
d. What are the users attitude towards the website? The users were very responsive to the website because they saw that the site was saving time and also money.
3. C - Choose the evaluation paradigm and techniques to answer the questions.
This looks at how the data is analyzed and presented
a. Quick and dirty – designers informally get feedback from users or constants to confirm that their ideas are in-line with users’ needs and are done any time.
b. Predictive evaluation – experts apply their knowledge of typical users to predict usability problems. Users need not to be present.
c. Usability testing – the performance of the typical users is recorded, the users are watched on video, evaluation on the users is done, user satisfaction is done lastly
d. Field studies – this is done in the natural settings to understand what users do naturally and how technology impacts no them.
The paradigm that was used was quick and dirty because the users were involved in every step of the design process and it is usually done at any time.
4. I - Identify the practical issues.
You are going to look at some of the things like
How to select users
How to stay on budget
How to stay on schedule
How to find evaluators
How to select equipment
5. D - Decide how to deal with the ethical issues.
a. The users will have the privacy of their private information and will not be disclosed to any one unless with the consent of the user
b. The users will be able to leave the site at any time that they wish i.e. they can be able to discontinue their membership at their own wish
c. The user will be treated politely but they have to follow the rules and regulations of the website.
d. The users will have the right to know the goals of the study
6. E - Evaluate, interpret and present the data
The data is analyzed and interpreted using the quick and dirty paradigm and technique.
The findings can be generalized on our part the evaluation was both formative and summative.
Wednesday, March 12, 2008
DOCUMENTATION OF SEMESTER PROJECT
STRATHMORE UNIVERSITY
FACULTY: INFORMATION TECHNOLOGY
COURSE: BACHELOR OF BUSINESS INFORMATION TECHNOLOGY
ASSIGNMENT: HCI PROJECT (ONLINE BOOKSHOP WEBSITE)
COURSE UNIT: HUMAN COMPUTER INTERACTION
GROUP MEMBERS:
1) MULILI NZUKI 008402
2) MOGENI JOY 045439
3) CHARLES NDETE 008455
4) KARANJA ALEX 008428
5) MUNYOKI CAROLINE KAYOKA 008401
PRESENTED TO: MR.P. OKECH
DATE OF SUBMISSION: 12TH MARCH 2008
INTRODUCTION
Going physically to different bookshops to buy and compare prices of books is very cumbersome and time consuming. Our proposed system is a website that will enable users buy books from different bookshops that will be made available on-line. This will reduce the time a consumer will use since he can purchase any book from any bookshop at his own convenient time and place e.g. from his/her office, house etc
Different stakeholders will access the website
Justification
There are several benefits of implementing a website for on-line purchase of books as stated below.
On- line purchase saves the customers’ time and is efficient.
Bookshops will effectively manage purchases and deliveries.
Helps the stakeholder in decision making
Easy tracing of books available at different bookshops
Book categories help in making the search process easier and faster.
Reduced cost of advertising
Advertisements will enable the customers’ find out the latest books available.
Customers can easily compare prices of books at different bookshops.
Activities performed
The activities carried out include:
§ Identifying the various stakeholders of the website and the different roles they will play.
§ Identifying the functional, non-functional, data, user, environmental and usability requirements from a range of potential users and analysis these requirements focusing on what the user wants.
§ Coming up with scenarios to show a step-by-step process of navigating through the website.
§ Using the scenarios, we were able to develop a low-fidelity prototype which the potential users evaluated and gave their views on whether they understood the process or the website would be easy to use once developed. The low-fidelity prototype was developed using index cards to show how a page on the website would look.
§ Development of a high-fidelity prototype using Macromedia Dreamweaver to further show how the navigation of the website from page to page e.g. making the menu easier to use.
Stakeholders and the goals they are meant to achieve while interacting with the system
1) Customers (both internal and external)- they will interact with the system and be able to buy books from the different bookshops available on line.
2) Suppliers- they will be able to identify available bookshops and deliver books to the different bookshops available.
3) Writers- they will show different books that they have written that will be made available online.
4) Delivery staff- these are the people who will do the actual delivery of books to the customers after purchase and update a given bookshop's stock record once delivery is made.
5) Advertisers/marketers - they will be able to advertise new books that are available so that each bookshop can decide on what and where to buy.
REQUIREMENT ANALYSIS
List of requirements
· Functional requirements
· Non- functional requirements
· Data requirements
· Environmental requirements.
· User requirements
Functional requirements
1) The website will enable different bookshops to sell their books on-line.
2) The website will list all the different books available.
3) The website will enable bookshops sell books to a wider geographical market or even to the neighboring countries
4) Different books will be advertised in this website.
Non- functional requirements
1) A large database will be provided for each bookshop.
2) The books should be delivered as soon as the customers have made their payments.
3) Delivery should be made as early as 5 days and as late as 8 days.
Data requirements
1) The customer information should be stored.
2) The information about the bookshop and the books that they have in stock should be stored.
3) Information about payments made and books bought should be stored.
4) All information should be stored in a database.
5) Information about deliveries made by suppliers should also be stored.
Environmental requirements.
1) There should be privacy about information stored about users e.g. information about credit card details.
2) There should be no sharing of files across different bookshops.
3) Customer details should not be shared with others bookshops’ sites.
User requirements
1) The system should be user friendly to both expert and novice users.
2) The system should show the books the user has bought.
3) The system should also show books in the user's shopcart but which the users have not yet paid for.
System requirement priorities using MoSCoW:
Must include
i) The website will have a list of available bookshops to enable users identify where they can buy books from
ii) An online registration will be made available, to allow users register in the site.
iii) The website will list all the books available and their respective prices.
iv) A large database will be provided for each bookshop so as to allow storage of information about bookshops. .
v) Login button to allow users to login into the site.
vi) Search button to allow users to search for bookshops and books
vii) There should be privacy about information stored about users e.g. information about credit card details. This will prevent fraud.
Should include
i) Information about payments made and books bought should be stored.
ii) The sell books to a wider geographical market, to attract more customers and increase sales.
iii) The system should have shopcart to allow users make purchases.
Could include
i) A list of the books the user has bought.
Would include
i) Advertisements for different books available on-line. This will enable users identify new books in the bookshops.
TASKS
1) Giving details of several bookshops and the books that they have in the stores. The bookshop will give details of books available and their prices.
2) Selling and advertising books to various customers. The website will allow customers get free membership and make them aware of arrival of new books.
3) Comparing prices from different bookshops and customers will find out where to get the best discount offers. Customers can search for a book through simple or advanced searches and find out which bookshop stocks that particular book.
4) Ensuring books are paid for before delivery. For users to pay for the books, they must be registered members. The user will be allowed to use credit or debit cards.
5) Reducing the labor force in the bookshop and search for a wider market.
HIERARCHICAL TASK ANALYSIS
The following hierarchical task analysis will be used so as to break down the task of buying a book into sub-tasks.
0) In order to buy a book from any bookshop in the website
1) Log in to the website
2) Search for a bookshop
2.1) Access the book categories
2.2) Search for a particular book.
2.3) Identify the price of the book
2.4) Add to your shopping cart
3) Enter your account details
4) Confirm your account details.
6) If details are valid, wait for delivery of the books
The HTA –graphical
Buy a book from the website 0
Log in to the website 1
Search for a bookshop
2
Enter your account details
3
Confirm account details
4
Access the book categories
2.1
Search for a particular book
2.2
Identify the price of the book
2.3
Add to your shopping cart
2.4
Scenario:
A user locates the site. After finding the site, he will be able to search for a bookshop since a list of many bookshops (drop down menu) will be provided. The search can be done using a simple search i.e. the user enters the book name, or he can use an advanced search i.e. he enters the book name, ISBN number, author, year of publish and place where the book was published. A user can also click into an advert so that he can view the list of new books that are available.
A user cans login into the site. After a successful login, the user’s account will be loaded. The user’s account will show user details such as: his name, details of his purchases, books that the user has not checked out and will allow users to enter complaints or questions. Registered users will be allowed to buy books from any bookshop in the site. Once a user identifies a book, he can add it to his shopping cart. After adding to the shop cart, he is allowed to order the book and he has to fill in a form that will contain the delivery details. The user will enter his account information, which will be crosschecked for validity. Then payment is processed and the books will be delivered to the customers within a period of one week. Non- registered users will be forced to register into the site so that they can be allowed to make purchases.
DESIGN
LOW FIDELITY PROTOTYPE
A conceptual model was used. It described what the proposed system would do, behave and look like in a manner that was understood by the users
The steps used were:
i) Identifying what the users would do when carrying out their tasks
ii) How the proposed system would support these tasks
iii) Identifying what kind of interface metaphor was appropriate- used to map users familiar knowledge with unfamiliar knowledge.
iv) Identifying what kind of interaction modes and styles will be used
Low fidelity prototyping involves using a medium unlike the final medium. Two different prototypes were drawn on manila papers presented to the user and the users were meant to choose toe best interface among the two so that the actual design of the interface would continue.
1) HIGH FIDELITY PROTOTYPE
It uses materials expected in the final product. A web authoring tool, DreamweaverMX was used to design the interface. Some considerations that were made include:
Screen layout, Colors, navigation etc
Some principals/ rules that were put into consideration while designing the interface are:
· Visibility- making visible all the relevant parts of the system
· Constraints- restricting what can or cannot be done
· Affordance- properties of the system that determine how it will be used
· Mapping- controls should be easy to interpret
· Feedback
· Consistency- similar operations use similar elements for similar tasks
EVALUATION
Evaluation is a process that involves gathering about the usability of the design by a specified group of users for a particular activity within a specified environment.
Evaluation was carried out during the design of the online bookshop website to understand the real world and determine if it achieves the goals of the desired users. There were two low fidelity prototypes to be valuated o that the best alternative could be chosen by users. The students and lecturer also evaluated the high fidelity prototype.
Types of evaluation
Formative evaluation-This is done at different stages of development to check products meet the user needs. Formative evaluation was carried out on the low fidelity prototypes as well as the high fidelity prototype.
Summative evaluation-This evaluation takes place after implementation and has the aim of testing the proper functioning of a product. This evaluation was carried out on the hgh fidelity prototype.
The DECIDE framework was used to guide the evaluation. It involved:
1) Determining the goals of evaluation: this was meant to assist in identifying the strengths and weaknesses of the system.
2) Exploring specific questions that need to be answered.
3) Choosing evaluation techniques and paradigms to answer those questions.
4) Identification of practical issues.
5) Deciding on how to deal with ethical issues
6) Evaluating, interpreting and presenting the data gathered.
Goals achieved after evaluation
Safety-information on the website is only accessible to authorized users and there is assured security of data.
Utility-The website provides information such as location of the various bookshops, their prices and even the type of books sold including other necessary information.
Effectiveness-Due to the information provided on the website, a user is able to achieve his or her goals on a getting information about what they are looking for.
Efficiency-The presence of links enables the user access various web pages as quickly as possible to get the intended information.
Techniques used.
The technique used for evaluation was asking users about their opinion using the low fidelity prototypes made. The best alternative chosen by the desired users was then implemented.
CONCLUSION
Lessons learnt
1) Human Computer Interaction is a discipline concerned with the design, evaluation and implementation of interactive computing systems for human use.
2) It is important to know and understand the psychological and physiological abilities and limitations of human beings
3) It is important to understand the background, tasks, mindset, and experiences of users.
4) Interaction modes and interface metaphors provide a structure for thinking about which kind of conceptual model to develop
5) Getting requirements right is crucial
References:
1) Sharp Helen, Rogers Yvonne, Preece jenny (2006). Interaction Design: Beyond Human Computer Interaction (2nd Ed.) Wiley
2) Preece Jenny, et. al. (1995). Human Computer Interaction (3rd Edition). Addison-Wesley publishing
3) www.google.com
4) Class notes
FACULTY: INFORMATION TECHNOLOGY
COURSE: BACHELOR OF BUSINESS INFORMATION TECHNOLOGY
ASSIGNMENT: HCI PROJECT (ONLINE BOOKSHOP WEBSITE)
COURSE UNIT: HUMAN COMPUTER INTERACTION
GROUP MEMBERS:
1) MULILI NZUKI 008402
2) MOGENI JOY 045439
3) CHARLES NDETE 008455
4) KARANJA ALEX 008428
5) MUNYOKI CAROLINE KAYOKA 008401
PRESENTED TO: MR.P. OKECH
DATE OF SUBMISSION: 12TH MARCH 2008
INTRODUCTION
Going physically to different bookshops to buy and compare prices of books is very cumbersome and time consuming. Our proposed system is a website that will enable users buy books from different bookshops that will be made available on-line. This will reduce the time a consumer will use since he can purchase any book from any bookshop at his own convenient time and place e.g. from his/her office, house etc
Different stakeholders will access the website
Justification
There are several benefits of implementing a website for on-line purchase of books as stated below.
On- line purchase saves the customers’ time and is efficient.
Bookshops will effectively manage purchases and deliveries.
Helps the stakeholder in decision making
Easy tracing of books available at different bookshops
Book categories help in making the search process easier and faster.
Reduced cost of advertising
Advertisements will enable the customers’ find out the latest books available.
Customers can easily compare prices of books at different bookshops.
Activities performed
The activities carried out include:
§ Identifying the various stakeholders of the website and the different roles they will play.
§ Identifying the functional, non-functional, data, user, environmental and usability requirements from a range of potential users and analysis these requirements focusing on what the user wants.
§ Coming up with scenarios to show a step-by-step process of navigating through the website.
§ Using the scenarios, we were able to develop a low-fidelity prototype which the potential users evaluated and gave their views on whether they understood the process or the website would be easy to use once developed. The low-fidelity prototype was developed using index cards to show how a page on the website would look.
§ Development of a high-fidelity prototype using Macromedia Dreamweaver to further show how the navigation of the website from page to page e.g. making the menu easier to use.
Stakeholders and the goals they are meant to achieve while interacting with the system
1) Customers (both internal and external)- they will interact with the system and be able to buy books from the different bookshops available on line.
2) Suppliers- they will be able to identify available bookshops and deliver books to the different bookshops available.
3) Writers- they will show different books that they have written that will be made available online.
4) Delivery staff- these are the people who will do the actual delivery of books to the customers after purchase and update a given bookshop's stock record once delivery is made.
5) Advertisers/marketers - they will be able to advertise new books that are available so that each bookshop can decide on what and where to buy.
REQUIREMENT ANALYSIS
List of requirements
· Functional requirements
· Non- functional requirements
· Data requirements
· Environmental requirements.
· User requirements
Functional requirements
1) The website will enable different bookshops to sell their books on-line.
2) The website will list all the different books available.
3) The website will enable bookshops sell books to a wider geographical market or even to the neighboring countries
4) Different books will be advertised in this website.
Non- functional requirements
1) A large database will be provided for each bookshop.
2) The books should be delivered as soon as the customers have made their payments.
3) Delivery should be made as early as 5 days and as late as 8 days.
Data requirements
1) The customer information should be stored.
2) The information about the bookshop and the books that they have in stock should be stored.
3) Information about payments made and books bought should be stored.
4) All information should be stored in a database.
5) Information about deliveries made by suppliers should also be stored.
Environmental requirements.
1) There should be privacy about information stored about users e.g. information about credit card details.
2) There should be no sharing of files across different bookshops.
3) Customer details should not be shared with others bookshops’ sites.
User requirements
1) The system should be user friendly to both expert and novice users.
2) The system should show the books the user has bought.
3) The system should also show books in the user's shopcart but which the users have not yet paid for.
System requirement priorities using MoSCoW:
Must include
i) The website will have a list of available bookshops to enable users identify where they can buy books from
ii) An online registration will be made available, to allow users register in the site.
iii) The website will list all the books available and their respective prices.
iv) A large database will be provided for each bookshop so as to allow storage of information about bookshops. .
v) Login button to allow users to login into the site.
vi) Search button to allow users to search for bookshops and books
vii) There should be privacy about information stored about users e.g. information about credit card details. This will prevent fraud.
Should include
i) Information about payments made and books bought should be stored.
ii) The sell books to a wider geographical market, to attract more customers and increase sales.
iii) The system should have shopcart to allow users make purchases.
Could include
i) A list of the books the user has bought.
Would include
i) Advertisements for different books available on-line. This will enable users identify new books in the bookshops.
TASKS
1) Giving details of several bookshops and the books that they have in the stores. The bookshop will give details of books available and their prices.
2) Selling and advertising books to various customers. The website will allow customers get free membership and make them aware of arrival of new books.
3) Comparing prices from different bookshops and customers will find out where to get the best discount offers. Customers can search for a book through simple or advanced searches and find out which bookshop stocks that particular book.
4) Ensuring books are paid for before delivery. For users to pay for the books, they must be registered members. The user will be allowed to use credit or debit cards.
5) Reducing the labor force in the bookshop and search for a wider market.
HIERARCHICAL TASK ANALYSIS
The following hierarchical task analysis will be used so as to break down the task of buying a book into sub-tasks.
0) In order to buy a book from any bookshop in the website
1) Log in to the website
2) Search for a bookshop
2.1) Access the book categories
2.2) Search for a particular book.
2.3) Identify the price of the book
2.4) Add to your shopping cart
3) Enter your account details
4) Confirm your account details.
6) If details are valid, wait for delivery of the books
The HTA –graphical
Buy a book from the website 0
Log in to the website 1
Search for a bookshop
2
Enter your account details
3
Confirm account details
4
Access the book categories
2.1
Search for a particular book
2.2
Identify the price of the book
2.3
Add to your shopping cart
2.4
Scenario:
A user locates the site. After finding the site, he will be able to search for a bookshop since a list of many bookshops (drop down menu) will be provided. The search can be done using a simple search i.e. the user enters the book name, or he can use an advanced search i.e. he enters the book name, ISBN number, author, year of publish and place where the book was published. A user can also click into an advert so that he can view the list of new books that are available.
A user cans login into the site. After a successful login, the user’s account will be loaded. The user’s account will show user details such as: his name, details of his purchases, books that the user has not checked out and will allow users to enter complaints or questions. Registered users will be allowed to buy books from any bookshop in the site. Once a user identifies a book, he can add it to his shopping cart. After adding to the shop cart, he is allowed to order the book and he has to fill in a form that will contain the delivery details. The user will enter his account information, which will be crosschecked for validity. Then payment is processed and the books will be delivered to the customers within a period of one week. Non- registered users will be forced to register into the site so that they can be allowed to make purchases.
DESIGN
LOW FIDELITY PROTOTYPE
A conceptual model was used. It described what the proposed system would do, behave and look like in a manner that was understood by the users
The steps used were:
i) Identifying what the users would do when carrying out their tasks
ii) How the proposed system would support these tasks
iii) Identifying what kind of interface metaphor was appropriate- used to map users familiar knowledge with unfamiliar knowledge.
iv) Identifying what kind of interaction modes and styles will be used
Low fidelity prototyping involves using a medium unlike the final medium. Two different prototypes were drawn on manila papers presented to the user and the users were meant to choose toe best interface among the two so that the actual design of the interface would continue.
1) HIGH FIDELITY PROTOTYPE
It uses materials expected in the final product. A web authoring tool, DreamweaverMX was used to design the interface. Some considerations that were made include:
Screen layout, Colors, navigation etc
Some principals/ rules that were put into consideration while designing the interface are:
· Visibility- making visible all the relevant parts of the system
· Constraints- restricting what can or cannot be done
· Affordance- properties of the system that determine how it will be used
· Mapping- controls should be easy to interpret
· Feedback
· Consistency- similar operations use similar elements for similar tasks
EVALUATION
Evaluation is a process that involves gathering about the usability of the design by a specified group of users for a particular activity within a specified environment.
Evaluation was carried out during the design of the online bookshop website to understand the real world and determine if it achieves the goals of the desired users. There were two low fidelity prototypes to be valuated o that the best alternative could be chosen by users. The students and lecturer also evaluated the high fidelity prototype.
Types of evaluation
Formative evaluation-This is done at different stages of development to check products meet the user needs. Formative evaluation was carried out on the low fidelity prototypes as well as the high fidelity prototype.
Summative evaluation-This evaluation takes place after implementation and has the aim of testing the proper functioning of a product. This evaluation was carried out on the hgh fidelity prototype.
The DECIDE framework was used to guide the evaluation. It involved:
1) Determining the goals of evaluation: this was meant to assist in identifying the strengths and weaknesses of the system.
2) Exploring specific questions that need to be answered.
3) Choosing evaluation techniques and paradigms to answer those questions.
4) Identification of practical issues.
5) Deciding on how to deal with ethical issues
6) Evaluating, interpreting and presenting the data gathered.
Goals achieved after evaluation
Safety-information on the website is only accessible to authorized users and there is assured security of data.
Utility-The website provides information such as location of the various bookshops, their prices and even the type of books sold including other necessary information.
Effectiveness-Due to the information provided on the website, a user is able to achieve his or her goals on a getting information about what they are looking for.
Efficiency-The presence of links enables the user access various web pages as quickly as possible to get the intended information.
Techniques used.
The technique used for evaluation was asking users about their opinion using the low fidelity prototypes made. The best alternative chosen by the desired users was then implemented.
CONCLUSION
Lessons learnt
1) Human Computer Interaction is a discipline concerned with the design, evaluation and implementation of interactive computing systems for human use.
2) It is important to know and understand the psychological and physiological abilities and limitations of human beings
3) It is important to understand the background, tasks, mindset, and experiences of users.
4) Interaction modes and interface metaphors provide a structure for thinking about which kind of conceptual model to develop
5) Getting requirements right is crucial
References:
1) Sharp Helen, Rogers Yvonne, Preece jenny (2006). Interaction Design: Beyond Human Computer Interaction (2nd Ed.) Wiley
2) Preece Jenny, et. al. (1995). Human Computer Interaction (3rd Edition). Addison-Wesley publishing
3) www.google.com
4) Class notes
PROJECT PROPOSAL
Our proposed system is a website that will enable users buy books from various bookshops that will be made available online.This will reduce the time a customer
Wednesday, March 5, 2008
SYSTEM REQUIREMENTS
List of requirements
A) functional requirements
1) The website has to sell books on-line.
2) The website will list all the books available.
3) The website will sell books to a wider geographical market or even to the neighboring countries
4) Different books will be advertised in this website.
B) Non- functional requirements
1) A large database will be provided for each bookshop.
2) The books should be delivered as soon as the customers have made their payments.
3) Delivery should be made as early as 5 days and as late as 8 days.
C) Data requirements
1) The customer information should be stored.
2) The information about the bookshop and the books they have should be stored.
3) Information about payments made and books bought should be stored.
4) All information should be stored in a database.
5) Information about deliveries made by suppliers should also be stored.
D) Environmental requirements
1) There should be privacy about information stored about users e.g. information about credit card details.
2) There should be no sharing of files across different bookshops.
3) Customer details should not be shared with others bookshops’ sites.
E) User requirements
1) The system should be user friendly to both expert and novice users.
2) The system should show the books the user has bought.
3) The system should also show books in the user's shopcart but which the users have not yet paid for.
System requirement priorities using MoSCoW:
Must include
i) The website should have a list of available bookshops to enable users identify where they can buy books from
ii) An online registration, to allow users register in the site.
iii) The website will list all the books available and their respective prices.
iv) A large database will be provided for each bookshop so as to allow storage of bookshops information. .
v) Login button to allow users to login into the site.
vi) Search button to allow users to search for bookshops and books
vii) There should be privacy about information stored about users e.g. information about credit card details. This will prevent fraud.
Should include
i) Information about payments made and books bought should be stored.
ii) The sell books to a wider geographical market, to attract more customers and increase sales.
iii) The system should have shopcart to allow users make purchases.
Could include
i) A list of the books the user has bought.
Would include
i) Advertisement of different books available. This will enable users identify new books in the bookshops.
A) functional requirements
1) The website has to sell books on-line.
2) The website will list all the books available.
3) The website will sell books to a wider geographical market or even to the neighboring countries
4) Different books will be advertised in this website.
B) Non- functional requirements
1) A large database will be provided for each bookshop.
2) The books should be delivered as soon as the customers have made their payments.
3) Delivery should be made as early as 5 days and as late as 8 days.
C) Data requirements
1) The customer information should be stored.
2) The information about the bookshop and the books they have should be stored.
3) Information about payments made and books bought should be stored.
4) All information should be stored in a database.
5) Information about deliveries made by suppliers should also be stored.
D) Environmental requirements
1) There should be privacy about information stored about users e.g. information about credit card details.
2) There should be no sharing of files across different bookshops.
3) Customer details should not be shared with others bookshops’ sites.
E) User requirements
1) The system should be user friendly to both expert and novice users.
2) The system should show the books the user has bought.
3) The system should also show books in the user's shopcart but which the users have not yet paid for.
System requirement priorities using MoSCoW:
Must include
i) The website should have a list of available bookshops to enable users identify where they can buy books from
ii) An online registration, to allow users register in the site.
iii) The website will list all the books available and their respective prices.
iv) A large database will be provided for each bookshop so as to allow storage of bookshops information. .
v) Login button to allow users to login into the site.
vi) Search button to allow users to search for bookshops and books
vii) There should be privacy about information stored about users e.g. information about credit card details. This will prevent fraud.
Should include
i) Information about payments made and books bought should be stored.
ii) The sell books to a wider geographical market, to attract more customers and increase sales.
iii) The system should have shopcart to allow users make purchases.
Could include
i) A list of the books the user has bought.
Would include
i) Advertisement of different books available. This will enable users identify new books in the bookshops.
Sunday, March 2, 2008
SCENARIO
A user locates the site. After finding the site, he will be able to search for a bookshop since a list of many bookshops (drop down menu) will be provided. The search can be done using a simple search i.e. the user enters the book name, or he can use an advanced search i.e. he enters the book name, ISBN number, author, year of publish and place where the book was published. A user can also click into an advert so that he can view the list of new books that are available. The user can also search by category so that if the user wants to see all the Christian books or drama books then the user will enter the category that he/she wants.
Also after entering the site, the user can go and search for a book without entering a specific bookshop site. This will produce all the bookshops that have that particular book where the user can compare the prices between the different bookshops that have that book.
A user can login into the site. After a successful login, the user’s account will be loaded. The user’s account will show user details such as: his name, details of his purchases, books that the user has not yet bought but in the shop cart and will also allow users to enter complaints or questions. Registered users will be allowed to buy books from any bookshop in the site. Once a user identifies a book, he can add it to his shopping cart. After adding to the shop cart, he is allowed to order the book and he has to fill in a form that will contain the delivery details. The user will enter his account information, which will be crosschecked for validity. Then payment is processed and the books will be delivered to the customers within a period of one week after the payment through the post office. Non- registered users will be forced to register into the site so that they can be allowed to make purchases.
Also after entering the site, the user can go and search for a book without entering a specific bookshop site. This will produce all the bookshops that have that particular book where the user can compare the prices between the different bookshops that have that book.
A user can login into the site. After a successful login, the user’s account will be loaded. The user’s account will show user details such as: his name, details of his purchases, books that the user has not yet bought but in the shop cart and will also allow users to enter complaints or questions. Registered users will be allowed to buy books from any bookshop in the site. Once a user identifies a book, he can add it to his shopping cart. After adding to the shop cart, he is allowed to order the book and he has to fill in a form that will contain the delivery details. The user will enter his account information, which will be crosschecked for validity. Then payment is processed and the books will be delivered to the customers within a period of one week after the payment through the post office. Non- registered users will be forced to register into the site so that they can be allowed to make purchases.
Subscribe to:
Posts (Atom)