The Student Room Group

A Level digital technology / ICT coursework

Had to make a booking and order system for a business. Doing the write up now on hardware and software requirements. I've noted some hardware required but have no clue what else to write? any feedback is much appreciated.
It really depends on how your booking and order system is intended to be used. Your hardware and software requirements would derive from the user requirements -- i.e. what are the constrants and considerations which will determine your choices of hardware and software, so that the system can run and be able to meet the user requirements?

For example, does it need to be portable so that someone can use it away from a desk? does it need to connect to any other systems? does it need to access anything over the internet? Does it need a way for users to be able to enter text? does it need to be able to print any documents? Does any part of it need to run on a server? does it run within a web browser? will it need to support any particular O/S or device? Are there any specific O/S features which are required? Does it need to be cross-platform? What about cost and 3rd-party licences? Are there any particular vendors which need to be supported or vendors which can't be used? What about patching and support for 3rd-party software? Does it need to be backward-compatible with any old legacy systems/software? What about security or privacy issues? What about accessibility (e.g. people with impairments/disabilities)?
(edited 5 years ago)
Reply 2
Original post by winterscoming
It really depends on how your booking and order system is intended to be used. Your hardware and software requirements would derive from the user requirements -- i.e. what hardware and software is actually needed in order for the system to run and users to be able to make use of the system?

For example, does it need to be portable so that someone can use it away from a desk? does it need to connect to any other systems? does it need to access anything over the internet? Does it need a way for users to be able to enter text? does it need to be able to print any documents? Does any part of it need to run on a server? does it run within a web browser? will it need to support any particular O/S or device? Are there any specific O/S features which are required? Does it need to be cross-platform? What about cost and 3rd-party licences? Are there any particular vendors which need to be supported or vendors which can't be used? What about patching and support for 3rd-party software? What about security or privacy issues?

I agree. It depends on the business and user requirements. What does the business sell? What products does the business need to order?
Here is an example of User Requirements and Non-functional requirements sections in a Requirements Document I prepared in one of my projects (you will of oc need to adapt it to your own software - it should be detailed, unambiguous, precise, meticulous, global, extensive and complete - technically, it is part of the first stage of the Software Development cycle (=Design), so you are doing it the wrong way round, but I suppose you now have no choice!



User Requirements Definition

1. to create a website that allows
marketing of its products

1.1. to list products by category and
subcategory

1.2. to show the prices of each product

1.3. to display features of each product

1.4. to record and display competitors’
prices when legally allowed

1.5. to visibly show special offers and
prices

1.6. to allow selection of 1-10 units of
any particular item

1.6.1. To have a drop-down menu to select
this number of units.

1.6.2. To produce an error message if number
of units not selected.

2. to advertise the company via its website

2.1. to make known the existence of the
company

2.2. provide the name and address of the
company

2.3. to provide contact details of the
company, e.g. telephone number, web address and e-mail contacts of major
customer service staff

2.4. to publicise the good intentions and
future goodwill and loyalty measures of the company

2.5. to display the logo of the company

2.6. to promote the excellent policies of
the company

3. to enable the customer to purchase
products that he/she wants

3.1. to allow simple search for basic
customers

3.2. to allow Boolean search for advanced
customers

3.3. to allow selection of favourable
products

3.4. to allow customers to view prices
before choice

3.5. to allow customers to add items to and
view basket

3.6. to allow customers to progress from
basket to check out


Non-functional requirements

Product (Usability)

1. To make it easy for the user to use
the website, and easy to navigate and to find information and pages.

1.1. Website should have clear but attractive look.

1.2. Website should be clear and not use colours
that strain the eyes of the user.

1.2.1. Arial font should be used throughout
for easy readability.

1.2.2. The colours used should be
complementary i.e. green (0, 255, 0 in hexadecimal code) should go with
magenta, red (255, 0, 0) with yellow, and blue (0, 0, 255) with orange.

1.2.3. Pictures should have a minimum
resolution of 800 X 500 pixels (0.4 megapixels).

1.3. Hyperlinks should be easy to locate and to follow.

1.3.1. With a typical western world internet
speed of 2-6 MB/s, transition between web pages should take a maximum of 0.3
seconds.

1.3.2. With a similar download speed of 1-3
MB/s, a picture of size 250KB should download in less than 0.5 seconds, so that
the customer can view product pictures quickly, and not be bored or distracted.

1.4. A clear site map should be created to inform
the user of its structure.

1.4.1. The site map should have the main categories:
products; contacts; Payment; Delivery and Information.

1.5. A well-designed hierarchy of web pages should
be used.

1.5.1. There should be no more than 3 levels
of hierarchy.

Product
(Security)

2. To have certain features in the
website package that reassure the customer

2.1. Security: the details of the customer,
particularly the password and credit/debit card details used for any purchase,
should be powerfully encrypted.

2.2. Security: The cvv number of the
customer’s card should not be stored, even if the customer opts for storage of
card details for future purchases.

Product (Efficiency)

3. To create a website that is easy to
find on searches, and to make it appear in the top five results of searches.

3.1. To have links to famous sites, i.e. Facebook, EBay
and Google.

3.1.1. To include the Facebook logo as a
link to Facebook.

3.1.2. To arrange with EBay to have a link
to Euro-SA website when a user of EBay searches an item on EBay that Euro-SA
stocks.

3.1.3. To open an account with Google
Adwords, and to ensure that the maximum visibility and searchability of the
website is enabled.

THIS IS PROBS FAR TOO ADVANCED FOR A LEVEL (it is equivalent to Level 6 = masters level: A level = Level 3/4), so do use a simplified version!!


Good luck!
Reply 4
thank you very much!! its for a gym. system has to allow users to book classes and order gym equipment.


Original post by winterscoming
It really depends on how your booking and order system is intended to be used. Your hardware and software requirements would derive from the user requirements -- i.e. what are the constrants and considerations which will determine your choices of hardware and software, so that the system can run and be able to meet the user requirements?

For example, does it need to be portable so that someone can use it away from a desk? does it need to connect to any other systems? does it need to access anything over the internet? Does it need a way for users to be able to enter text? does it need to be able to print any documents? Does any part of it need to run on a server? does it run within a web browser? will it need to support any particular O/S or device? Are there any specific O/S features which are required? Does it need to be cross-platform? What about cost and 3rd-party licences? Are there any particular vendors which need to be supported or vendors which can't be used? What about patching and support for 3rd-party software? Does it need to be backward-compatible with any old legacy systems/software? What about security or privacy issues? What about accessibility (e.g. people with impairments/disabilities)?
Reply 5
Nice tips. This information is vital for everybody. Thanks macpatgh-Sheldon could you please talk about cyber-security ?
Original post by macpatgh-Sheldon
Here is an example of User Requirements and Non-functional requirements sections in a Requirements Document I prepared in one of my projects (you will of oc need to adapt it to your own software - it should be detailed, unambiguous, precise, meticulous, global, extensive and complete - technically, it is part of the first stage of the Software Development cycle (=Design), so you are doing it the wrong way round, but I suppose you now have no choice!



User Requirements Definition

1. to create a website that allows
marketing of its products

1.1. to list products by category and
subcategory

1.2. to show the prices of each product

1.3. to display features of each product

1.4. to record and display competitors’
prices when legally allowed

1.5. to visibly show special offers and
prices

1.6. to allow selection of 1-10 units of
any particular item

1.6.1. To have a drop-down menu to select
this number of units.

1.6.2. To produce an error message if number
of units not selected.

2. to advertise the company via its website

2.1. to make known the existence of the
company

2.2. provide the name and address of the
company

2.3. to provide contact details of the
company, e.g. telephone number, web address and e-mail contacts of major
customer service staff

2.4. to publicise the good intentions and
future goodwill and loyalty measures of the company

2.5. to display the logo of the company

2.6. to promote the excellent policies of
the company

3. to enable the customer to purchase
products that he/she wants

3.1. to allow simple search for basic
customers

3.2. to allow Boolean search for advanced
customers

3.3. to allow selection of favourable
products

3.4. to allow customers to view prices
before choice

3.5. to allow customers to add items to and
view basket

3.6. to allow customers to progress from
basket to check out


Non-functional requirements

Product (Usability)

1. To make it easy for the user to use
the website, and easy to navigate and to find information and pages.

1.1. Website should have clear but attractive look.

1.2. Website should be clear and not use colours
that strain the eyes of the user.

1.2.1. Arial font should be used throughout
for easy readability.

1.2.2. The colours used should be
complementary i.e. green (0, 255, 0 in hexadecimal code) should go with
magenta, red (255, 0, 0) with yellow, and blue (0, 0, 255) with orange.

1.2.3. Pictures should have a minimum
resolution of 800 X 500 pixels (0.4 megapixels).

1.3. Hyperlinks should be easy to locate and to follow.

1.3.1. With a typical western world internet
speed of 2-6 MB/s, transition between web pages should take a maximum of 0.3
seconds.

1.3.2. With a similar download speed of 1-3
MB/s, a picture of size 250KB should download in less than 0.5 seconds, so that
the customer can view product pictures quickly, and not be bored or distracted.

1.4. A clear site map should be created to inform
the user of its structure.

1.4.1. The site map should have the main categories:
products; contacts; Payment; Delivery and Information.

1.5. A well-designed hierarchy of web pages should
be used.

1.5.1. There should be no more than 3 levels
of hierarchy.

Product
(Security)

2. To have certain features in the
website package that reassure the customer

2.1. Security: the details of the customer,
particularly the password and credit/debit card details used for any purchase,
should be powerfully encrypted.

2.2. Security: The cvv number of the
customer’s card should not be stored, even if the customer opts for storage of
card details for future purchases.

Product (Efficiency)

3. To create a website that is easy to
find on searches, and to make it appear in the top five results of searches.

3.1. To have links to famous sites, i.e. Facebook, EBay
and Google.

3.1.1. To include the Facebook logo as a
link to Facebook.

3.1.2. To arrange with EBay to have a link
to Euro-SA website when a user of EBay searches an item on EBay that Euro-SA
stocks.

3.1.3. To open an account with Google
Adwords, and to ensure that the maximum visibility and searchability of the
website is enabled.

THIS IS PROBS FAR TOO ADVANCED FOR A LEVEL (it is equivalent to Level 6 = masters level: A level = Level 3/4), so do use a simplified version!!


Good luck!
Good morning @LeahCruz
Looks like you are an early bird like me - you might have heard the old saying "The early bird gets the full English breakfast!" (Having said that, I still have to fry mine! :smile:).

Thank you for your kind words (I did not include the full requirements list (which was more than twice as long) in case some anti-nerds started cursing me :mad: - if you would like to view it, please PM me).

I think your confidence in my ability might be too enhanced! - I have an MSc in CS but not one in Computer Security (yet haha!) and did not take up the module in Computer Security in my CS course, so my knowledge is basic on this topic (terribly sorry!) - you must remember that I am not a clone of Sheldon (DIFFERENCES: a) I have a golden complexion [you could call it a congenital suntan if you like medical terminology!] b) My taste in women is very different - let us face it, his girlfriend is weird! c) [hopefully] my personality is much easier to get on with, etc.)

M

Quick Reply

Latest

Trending

Trending