Beruflich Dokumente
Kultur Dokumente
UOG.REG.NO 1
Acknowledgement
UOG.REG.NO 2
Table of contents
1. Introduction
-------------------------------------------------------------------------------------4
2. Section A -------------------------------------------------------------------------------------------5
A. DSDM would be an appropriate method to use with in PE -----------------------------6
3. Section B ------------------------------------------------------------------------------------------9
B1.1 Non-high-level requirements --------------------------------------------------------------10
B1.2 High-level requirements -------------------------------------------------------------------10
B2.1 prioritizing requirements by MoSCoW -------------------------------------------------14
B2.2 Explanation of prioritizing -----------------------------------------------------------------14
4. Section C ------------------------------------------------------------------------------------------17
C1. Need of a data controller ---------------------------------------------------------------------18
C2. Purpose of BCS code of conduct -----------------------------------------------------------20
5. Conclusion
---------------------------------------------------------------------------------------22
6. Reference
-----------------------------------------------------------------------------------------23
7. Bibliography ------------------------------------------------------------------------------------- 24
UOG.REG.NO 3
Introduction
According to the case study Paint everything (PE) is a medium sized company that manufactures
and sells paint. Two years ago managing director decide to improve sales by adding an online
store. So, companys IT team was appointed to the task. But year later the system was still not
completed and unfit for purpose and user requirements not being met. Three months ago newly
appointed managing director decide to start the project again. To complete the task company
requested the help of an external IT consultant, Sally flowers (SF) and also asked for her
assistance in recruiting an additional it team. Board meeting has been held and according to the
meeting the directors need to see a quick result, since the project has been running for long
period without any success and they need early justification. Most importantly they wanted a
basic system will be up running in 4 months time. New, MD hired an IT consultant to get help
on building a new system. This assignment is on the method that going to use to overcome the
PEs problem domain. (PE ltd case study).
UOG.REG.NO 4
Section A
UOG.REG.NO 5
Fig
1
AGILE
Methods
http://dsdmofagilemethodology.wikidot.com/
UOG.REG.NO 6
of
of
Software
Software
Development
Development
Iterative and incremental development. Not only in the PEs development process, its a risk
to all projects that to develop the whole system rather developing the system part by part. As
mentioned in the previous principles the mistakes can be happen and changes may need to be do
during the process. So, the iterative and incremental development is suitable for use within PE.
Otherwise it will cause more time to start over when a mistake has happen.
Testing is through the life cycle. Several techniques are using in the DSDM methodology, such
MoSCoW prioritization in a previous principle (requirements are base lined at a high level).
These techniques will clarify the work in DSDM development. So, in this principle time boxes,
at the end of each time box stake holders will have a common discussion to get the agreement for
the output. Not only the techniques also the framework of the life cycle will have number of
review stages to test whether has the development delivered the write output. As PE taking the
discussions with the stake holders (appendix B) its suitable to use DSDM methodology.
Communication and collaboration among all stake holders are essential. In order to follow
all above principles it is important to have regular communications and collaborations between
the stakeholders who involved to the development. As in the scenario PE works by facilitated
workshops. So, such activities going on PE it is suitable to have DSDM methodology to
overcome the solution of PE.
As explained DSDM methodology can be used to PEs development, because DSDMs
principles are most suitable for use within the development. Above explanation proves that and
DSDM is suitable for PE cause of such factors like PE needs fast development, need to meet the
exact user requirements and need early justification (DSDM uses prototypes).
In addition to the principles DSDM methodology use technique like Time boxing.
what can be achieved in the agreed timeframe ensures that Time boxes finish on time. So, this
will be most needed to complete the system of PE in short time period.
Section B
UOG.REG.NO 9
Managing director
From requirements which are mentioned by Scott Hardy I got bellow high-level requirements.
R1 Track orders and shipping
R2 Differentiate customers who are artists and who are doing home renovations
R3 Placing order
R4 Clients may have facility to rate and give feedback on products
In here R1 gives the main functions that should be in the system. User should be able to track the
orders and track the shipping of the products. At it should be in the system, R1 is high-level
requirement. R2 It tells system should separate customers who are artists and who are doing
home renovations. As in the scenario those are target customers of PE. System should identify
the customers properly to provide a good service to them. So, this makes R2 high-level
requirement that should be on the system. R3 placing orders, is another main function which
should be on the system. When a customer accessing the online store he should be able to place
the order at the moment, if he feels it is the right product which he want. After he received the
product he would be able to give a feedback on the product lately in the system. That makes R4
high-level requirement.
Finance
Following are the high-level requirements from the Wendy Lucass requirements list.
R5 - Monitor sales
R6 - Compare the revenue of different product lines
R7 - Links with social media
R8 - Eliminate the tick boxes, in the terms and conditions field.
As it is in the scenario the main purpose of the new system is to improve sales. To do that PE
must have clear idea about the sales. So, R5 function is high-level requirement which should be
on the system. Also PE able to compare the earnings of different product lines so they can give
more attention on poor revenue products. So, R6 is a function too which should be in the system
as a high-level requirements. R7 links with the social media, to improve sales marketing is
much needed thing. The function R7 should be in the system to make marketing easier to PE.
Tick boxes in the terms and conditions also a function usually in the online systems. But PE have
different view on that to eliminate the tick boxes to not annoy customers. This function can be
ignored as in R8 when developing system.
UOG.REG.NO 11
UOG.REG.NO 12
UOG.REG.NO 13
R9
R10
R11
R12
Making payments
Store card information
Return unsatisfied products
Search facility to find products
R13
R14
R15
R16
UOG.REG.NO 14
Requirement
Track orders and shipping
Differentiate customers who are artists and
who are doing home renovations
Placing order
Clients may have facility to rate and give
feedback on products
Monitor sales
Compare the revenue of different product
lines
Links with social media
Should have
Differentiate customers who are artists and who are doing home renovations R2
Clients may have facility to rate and give feedback on products R4
Links with social media - R7
Could have
Would have
UOG.REG.NO 15
As we follow DSDM attren development method to develop the system, the time to complete the
project has been fixed. So, identifying the pri
orities will help to complete the project within the dead line. As it is tool of DSDM atrem
methodology here we used MoSCoW prioritization to identify the requirements. Above I have
clearly shown the requirements in the each field in MoSCoW.
Must have field includes the most needed requirements that project is responsible for deliver
within the exact time period. This is more likely, project cant be completed without fulfilling
these requirements. So, complete the project it is must to complete following requirements R1,
R3, R5, R6, R9, R10, R11, R12 and R13.
Should have field includes the requirements that much important compared to should have and
wont have. But still project can be completed only with the Must have requirements. As
identified R2, R4 and R7 are the Should have requirements.
Could have requirements are less important comparing to the should have requirements.
Considering the requirements mentioned in could have field R15, R16 and R14 are the
requirements that can have within the system but without it there will be no impact to the system.
Wont have includes the requirements that project will agreed to not deliver or not to deliver in
this time. As it is in the case study PE asking to R8 within the system. So, directly development
team can ignore this requirement.
Source - MoSCoW Prioritization, URL - http://www.dsdm.org/content/10-moscow-prioritisation
UOG.REG.NO 16
Section C
UOG.REG.NO 17
Information must be retention which is to be kept no longer than necessary for stated
purpose. To operate with the PEs system customers have to be sign up. To proceed a complete
buying of a product he or she has to sign up and store card information. So, the gathered
information will be on the system until the customer completely sign off with the system, which
is no longer connect with the system. Purpose of the information of particular customer is no
longer necessary. So, the information can be archived.
Always processing information with respect to the rights of the data subject. The first
example that I have given was string Card information. Considering this, the owner of the
information profile may ask to see the data, what PE kept. Customer must have that right to gain
full confident about the company. Otherwise this will cause issues to the company.
The information must be safe and secure. PE must guarantee that necessary technical and
organizational measures has taken against loss, damage, disclosure and unlawful use. If
information about the customers are not secure it can be misuse and can cause lot of damage to
customers and that will make legal issues to PE. So, to overcome that the information must be
secure and safe.
The information should not be transferred outside European Union unless adequate level
of protection to the rights of the subject. Which means if the data is to be transfer it have to
fulfil some conditions and rights of the PEs customers.
As above data controller will comply with these principles and he will make PE to overcome the
legal, social, ethical and professional issues.
Source - A Guide for Data Controllers,
URL - https://www.dataprotection.ie/documents/forms/NewAGuideForDataControllers.pdf
Source - Guidance: Data Controllers responsibilities,
URL - https://www.justice.gov.uk/downloads/information-access-rights/data-sharing/annex-gguidance-data-controllers.pdf
UOG.REG.NO 19
do so. As an example he shall not make statements to represent in the developing system on
behalf of the BCS unless authorized to do.
Professional Competence and integrity
According to the BCS code of conduct the system developers shall look to upgrade their
knowledge and shall maintain the awareness of technological development procedures which are
particular to their field. As to the code of conduct the developers shall not undertake any of work
or not agree to provide service that is not within their professional. As example PE needs to
develop online system, so the developers who undertaking the project should possess a web
development skills. Regarding to the example the developers shall observe the relevant BCS
code of practices which in his decisions are relevant.
As above the four section of BCS code of conduct show the professional issues that a system
developers contracted to PE may have to consider before he undertake the project.
Source - BCS the Chartered Institute for IT, Trustee Board Regulations - Schedule 3, Code of
Conduct for BCS Members
URL - http://www.bcs.org/upload/pdf/conduct.pdf
UOG.REG.NO 21
Conclusion
In this assignment it includes the PE Companys new system development. First I have
mentioned DSDM method is an appropriate method to use within PEs development process.
Then I have done the requirement categorizing. There I have identified high-level and non-highlevel requirements and I prioritized the requirements according to MoSCoW. Next it includes the
need of a data controller to the company and how it will help to LSPE issues. Finally the purpose
of BCS code of conduct and explained about the four section of BCS code of conduct which may
the contractor who contracted to PE need to consider.
UOG.REG.NO 22
Reference
AGILE Methods of Software Development - http://dsdmofagilemethodology.wikidot.com/
Fig 1 - AGILE Methods of Software Development http://dsdmofagilemethodology.wikidot.com/
Fig 2 Time boxing - http://www.dsdm.org/content/13-timeboxing
MoSCoW Prioritization, URL - http://www.dsdm.org/content/10-moscow-prioritisation
A Guide for Data Controllers,
URL - https://www.dataprotection.ie/documents/forms/NewAGuideForDataControllers.pdf
Guidance: Data Controllers responsibilities,
URL - https://www.justice.gov.uk/downloads/information-access-rights/data-sharing/annex-gguidance-data-controllers.pdf
BCS the Chartered Institute for IT, Trustee Board Regulations - Schedule 3, Code of Conduct for
BCS Members, URL - http://www.bcs.org/upload/pdf/conduct.pdf
UOG.REG.NO 23
Bibliography
Functional vs. Non Functional Requirements - http://reqtest.com/requirements-blog/functionalvs-non-functional-requirements/#conversion-0
UOG.REG.NO 24