22/B. P3- Produce a requirements specification to meet the business
and computing requirements of an identified organisation
In this document, Requirements for business or its product needs will be shown e.g., what a
product should look like, what are features it should contain, and what are the benefits of it
and costs of it. How effective it will be, how it will serve the audience or customer
Requirements for E-card organisation
Services provided by the organisation - The organisation offers services such as online designer
greeting cards, which are sent to the customers. Currently, the system used by organisation
does not allow customers to get customised or their desired cards.
The organisation’s goals – the organisation’s biggest aim is to gain upper hand in share market
of the online greeting card market.
Client’s needs, expectations, delivery of the ecards – the ecards are entirely online, file of the
card gets transferred to oxford for printing process or to upload on social media Needs of staff,
patterns, and style of working – Despite the fact that Cartes de Mode operates 24 hours a day
employees will be required to work Monday to Friday because this is when delivery businesses
and the post office are open.
Employees, clients, offices, market/service, and dispatch point locations — The central office is
in London, and the card printing centre is in Oxford, with employees based in both locations.
Customers come from all around the United Kingdom. The market is online-based, and the
regional postal service will be the distribution location.
Several factors that might affect the success and failure of the new ecard system
The costs and time for this system needs to be calculated carefully as this might be turning
point of success and failure. If time is not calculated then delay in project will cost the
organisation. Secondly, if costs are not calculated properly and carefully then it will cause
disturbance in flow of work and nobody will know how much money is invested. Costs and time
should be calculated right from the beginning. There are risks correlated with the tasks being
completed on time and within budget. As developing and creating the entire new system will
require more time and if more time will be spent which will cost more money and reduce
income. E-card systems may need maintenance on regular basis which will need 2 extra
members to maintain it and the staff should have the skill to do it. factors like changes in
management involvements of users in developing process may cause disturbance in original
plan.
Scope and Boundaries
,The e-card system needs to have long range in offering services/cards to the customers such as
Christmas cards, Eid cards, wedding cards, birthday cards, valentine's day or thank you cards.
Furthermore, different facilities should be given or provided to the customers such as
personalising cards, uploading images and posting on social media.
The e-card should have range of things to offer to the customers, this system should be able to
Access a quick view of events and reminders, access a quick view address book, create a diary
to keep track of events such as birthdays, three days before the event, send automatic calendar
reminders. Furthermore, it should be able to Include a link to your favourite social media
platform. Moreover, it should be able to be Viewable on mobile and desktop computers, from
the desktop, send e-cards, get a confirmation of your card receipt, make use of payment
options, use a password that isn't easily guessable
Boundaries may contribute in success and failure of a system. We need to know what are the
boundaries in e-card system. The boundaries for e-card system should include, the importance
of client and the system, Customer account information in the system's database, Animated
cards in the system's database, social media sites and the system and lastly Payment options
and the system.
Inputs and outputs
These two play a vital part in success and failure of e-card system as it notices every step or
detail of inputs what goes into the system and how a customer will be able to choose a card
and make payment. Here is list of inputs which are needed to make this system work efficiently.
These are inputs a system needs to have to make a process fluent and ecard system successful.
first you need to put Login information for customers, choosing a card, Card with text and
photographs, use social media to share, Entries in the diary, contact information in the address
book, Confirmation of payment by card, making payment and type of delivery.
Outputs are details or a step which shows the result after going through the inputting
information process such as, Notifications for important dates in your calendar, The final card
design, Access to the address book, Creating the card, shared via social media, Payment has
been confirmed, Delivery has been confirmed.
These are the all outputs which will appear after using inputs successfully being inputted.
Processes
The processes are the crucial part of the system and it is one of the most significant factors
because to reach all this step a developer must go through many steps such as looking at scope,
boundaries, inputs/outputs to make the processes smooth, fluent and errorless. So, what are
the processes which takes so many things and time to get ready for use?
, Here are the processes; Login into the system, look through the diary, make an entry in the
diary, look through your contact list, then include your mailing address, after that Adjust the
payment process, decide on the type of card you want to make, such as birthday, Valentine's
Day, etc., then select a card type category, such as amusing, serious, or a combination of the
two, include a photo card in your submission, select a card size, pick a family member, then
select whether or not to post to social media, make a purchase, Transactions has been
received.
These are all steps or inputs to make a purchase for an ecard. These are the steps which shows
how a successful ecard system works and provides fluent processes for customers.
Risks and constraints
There are risks and constraints in way to success of this e-card system. These are things which
are need to be checked before starting this project because for example if cost is not calculated
before the project begins then it will bring obstacles and hurdles in managing the pay of
workers and money being on the project.
There are different risks and constraints such as time, it's possible that additional time will be
required to finish some tasks, which will make it more expensive. There could also be
insufficient time to finish specific tasks, e.g., scheduling time scales may be miscalculated. Bugs
in the new system — After introducing a suitable e-card system, unusual defects may occur,
requiring time and effort to resolve. Employee competence - Some employees may lack the
necessary skills, competence to perform things, implying that doing so will take more longer to
accomplish them. Complete the task, or seek the assistance of a professional in that field that
would incur additional costs.
Future recommendations
Here are improvements or recommendation which can be made in the future. First, making the
e-card website intuitive. Website should be easy to use and understand for the customers so he
doesn’t find any difficulties in ordering things or simply using it for other purposes. Second, the
e-card website, alongside customer use, should be easy to use for the staff so they know when
to and how to update the information or fix the problem if occurs. Finally, system should be
checked on daily basis to find bugs or errors so the speed of it doesn’t get affected and flow of
it runs smoothly
Email to Mai Notte
