Development Frameworks and Methods (University of Greenwich BIT Coursework) by Nay Linn Ko

Development Frameworks & Methods

COMP - 1648 Page 1

Coursework Title : Development Frameworks and Methods

COMP 1648 : Development Frameworks and Methods

Due Date : 26th November 2015

Centre : KMD (Yangon, Myanmar)


COMP - 1648 Page 2

Acknowledgement

First of all, I like to acknowledge the responsible persons from University of Greenwich who provide this coursework for students. I would like to thank to all the authors and researchers who researched about Development Frameworks and Methods. Moreover, I would like to present my appreciation for our lecturer, Mr. Francis Murphy, for his great and expert lectures and guidelines. Last but not least, I would like to appreciate responsible teachers and staffs from our centre, KMD for providing such a good learning environment.


COMP - 1648 Page 3

Table of Contents Section A- Justifying DSDM as an appropriate development method .................................... 4

A 1. Management Summary for Youth Action ......................................................................... 4

A 1.1 Background ................................................................................................................ 4

A 1.2 Why is the project suitable with DSDM? .................................................................... 5

A 1.3 Benefits and Drawbacks of DSDM for the Project ...................................................... 7

Section B- High Level Requirements Analysis and MoSCoW Prioritisation ......................... 8

B 1. High Level Requirements Analysis .................................................................................. 8

B 1.1 Inappropriate Requirements for High Level ................................................................ 8

B 1.1.1 Inappropriate Functional Requirements for High Level ....................................... 8

B 1.1.2 Inappropriate Non-Functional Requirements for High Level ................................ 9

B 1.2 Appropriate High Level Requirements ...................................................................... 10

B 1.2.1 High Level Requirements that are hiding in the case study ................................ 11

B 1.2.2 Complete High Level Requirements List ........................................................... 12

B2. MoSCoW Prioritisation................................................................................................... 14

B 2.1 Updated High Level Requirement List with Priorities ............................................. 14

B 2.2 Reasons in Setting Priorities .................................................................................... 15

B 2.3 Incremental Delivery ............................................................................................... 18

Section C- Legal, Social, Ethical and Professional Issues ...................................................... 21

C1. Management Summary for Obligations of the Data Controller ........................................ 21

C 1.1 Role of a Data Controller...................................................................................... 21

C2. Management Summary for Purpose of the BCS Code of Conduct ................................... 24

Appendix ................................................................................................................................. 26


COMP - 1648 Page 4

Section A- Justifying DSDM as an appropriate development method

A1. Management Summary for Youth Action

According to the case study, Youth Action is a charity that supports young people through variety of projects. It has 45 full time employees, along with volunteers and the young people. Youth Action has 25 different service centres in South of England and a Service Centre Director is dedicated to manage each service centre. Moreover, there are three Regional Managers in Youth Action. One Regional Manager looks for 8 or 9 different service centres.

Each service centre is operating one or more projects. The operations of funds, the employment of the staffs are managed by Service Centre Director. The centres are funded by the local authority or other charitable donations.

` Youth Action Trust Board which consists of Chief Executive, the Finance Director and five individuals from the community is responsible to oversight the charity. There is also an Executive Committee in order to manage day to day operations.

A 1.1 Background

Youth Action has purchased central IT systems for the finance and marketing. But the systems are not integrated each other. Therefore, the management concerns about the systems recently. The charity was advised to invest in the purchase or development of Management Information Systems.

A project called Dig-it project, is to take youths to involve in helping to look after the gardens of the elderly. The project consists of one full time staff, 10 volunteers and about 30 young people. Young people in groups of 3 or 4 and each group is led by one volunteer. The project is funded by a local authority. Currently, Youth Action wants to record the necessary data for the local authority. Therefore, they would like to have a management information system that can manage allocation of young people to the teams, sending teams to help the gardens of the elderly.

According to the scenario, we could assume that Dig-it project is a small project. The Executive Committee of Youth Action has decided to develop a Management Information System for Dig-it Project as a pilot project. The Executive Committee wants the prototype system for the project within 4 months. Sandra Lee (Case worker of the service centre) and Hugh Sterling (Service centre manager) are the key persons in processing the project. The processes are generally simple and not computationally complex. The project is not a real-time or safety critical project.


COMP - 1648 Page 5

Because of the above reasons, his management of Youth Action believes that DSDM Atern would be the perfect approach for the development. Therefore, throughout this report, we would discuss about why DSDM has chosen as an appropriate method, high level functions of Dig-it project and legal, ethical and professional issues for the project.

A 1.2 Why is the project suitable with DSDM?

The unique concept of DSDM is usually defined by DSDM Consortium. The followings are the characteristics of projects that are suitable with DSDM Atern. (Ref: DSDM Consortium (2010), “The DSDM Atern Student Workbook”)

1. Focus on the business need

According to the scenario, Dig-it project is bringing together the needs of the elderly and helping to rehabilitate young people with social problems. It does not deal with human lives. If there are some mistakes in the system, the impacts could be able to accept. Dig-it project is not a real-time or safety critical project. The business case is servicing. DSDM approach is perfect for servicing business. Therefore, by using DSDM approach, we could more focus on the business needs.

2. Deliver on time

The transactions in Dig-it project could be breakable into blocks. So, we could use time-boxing techniques of DSDM. For example, registration process for first time box and producing reports for next time boxes. And the product must be delivered on time at the end of each time box since the deadlines of time-boxes in DSDM are immovable.

3. Collaborate

Collaboration of development team is critical in order to develop a successful MIS system according to DSDM. Youth Action is required to support facilitated workshops in which different stakeholders from both business and IT firm would be participated. In this case, Youth Action has supported facilitated workshops as we seen in appendix C.


COMP - 1648 Page 6

4. Never compromise quality

According to the case study, Dig-it project could be assumed as small project. The functionalities in the Dig-it project are simple and not computationally complex generally. Because of the project is small and simple, we could assume that the development team would not need to compromise quality. And, they can adjust the functionality rather than quality.

5. Build incrementally from firm foundations

Incremental development concept of DSDM is very useful that business can give feedbacks based on delivery and the final product would be in line with the business needs. The transactions of Dig-it project could be breakable and therefore, incremental development and delivery is possible.

6. Develop iteratively

DSDM allows changes so that business can change their requirements during developing period. MIS system for Dig-it project could be developed iteratively when feedbacks are returned at the end of an incremental delivery.

7. Communicate continuously and clearly

Youth Action had held facilitated workshops in order to provide continuous communications between the development team and the business. The transactions in the Dig-it project are possible to display using prototypes. By using prototypes, communicating with users and receiving feedbacks will be easy.

8. Demonstrate control

According to DSDM, the project must be controlled at all times. The incremental delivered product and iterative development processes must be visible to all stakeholders. By providing facilitated workshops, the project would be under control from all stake holders.


COMP - 1648 Page 7

A 1.3 Benefits and Drawbacks of DSDM for the Project

The followings are the benefits that could be achieved by Youth Action using DSDM Atern.

The executive committee of Youth Action is not needed to concern about work done since the development team is self-empowering.

Sandra Lee (Case worker) and Hugh Sterling (Service centre manager) are more likely to feel the ownership of the system because they also take part in the development process.

The project is separated into smaller projects which are processed independently so that an error in a small project could not harm the whole project.

Prototypes help users to understand the system and easy to provide the feedbacks. MoSCoW prioritisation allows important transactions to finish first within a fixed time

box.

Although DSDM Atern is suitable for Dig-it project, there are some drawbacks that could impact Youth Action Charity.

DSDM allows iterative development and the users might want to change their mind every time. A lot of iterations in the development process would consume time and budget.

Sometimes, it would be difficult to get a decision since the development team is self-empowering.

The users from the service centre may not want to take part in the development process such as workshops.


COMP - 1648 Page 8

Section B- High Level Requirements Analysis and MoSCoW Prioritisation

B 1. High Level Requirements Analysis

High level requirement is a business requirement which consists of a set of lower or middle level requirements. High level requirements are mostly critical business requirements. High level requirements would be better understood by the strategic and middle level management. For example- “Manage Data Entry” and “Control Operation” are kind of high level requirements which consist of a set of operations.

In this part, we would analyse about high level requirements which are existed in the Dig-it Project.

B 1.1 Inappropriate Requirements for High Level

During the last workshop, each stakeholder in Youth Action provided the list of their requirements for the new system. Some of these requirements are completely high level requirements and some are not. But, we want the list of high level requirements only in order to develop the new system. Therefore, we would list and annul the requirements which are not considered to be high level requirements.

See the detailed list of inappropriate requirements for high level in appendix, page no ( ).

B 1.1.1 Inappropriate Functional Requirements for High Level

A functional requirement describes what a software system should do. Functional requirements are related to the business operations. The stakeholders in Youth Action have mentioned functional requirements at the last workshop. But some of these functional requirements are not high level requirement.

For example- “Registration of young people” by Sandra Lee (Case Worker, Southeast London branch) is a functional requirement but it is not appropriate for high level requirement. This is because a high level requirement should be composed of a set of transactions. “Registration of young people” is included only the data entry transaction. Therefore, it is not a high level requirement.

Similar with “Registration of young people”, there are some other functional requirements that are not appropriate for high level requirement are composed during the workshop.


COMP - 1648 Page 9

B 1.1.2 Inappropriate Non-Functional Requirements for High Level

Non-functional requirements are defined mostly to elaborate the performance of a system. Most of the non-functional requirements should not be high level requirements because they are not business requirements. The requirements are considered to be optional.

For instance, “the system must be fast, user friendly and error free” by Kevin Marsh (Case Worker – North London) is a non-functional requirement. It is important to develop the system to be fast, user friendly and error-free. But, this is not a business requirement. Business still can run without these requirements. Management of Youth Action will not be interested in this requirement. Therefore, this requirement cannot be high level requirement although it is important.


COMP - 1648 Page 10

B 1.2 Appropriate High Level Requirements

Almost all High level requirements are functional requirements. Here is the list of the high level requirements which were discussed during the last workshop.

Requirement: Registration and management of volunteers, permanent staff, participating youths and elderly.

By: Rita Lester (External Systems Developer)

Importance : Managing the registration of volunteers, permanent staff, participating youths and elderly consists of a set of transactions. Functional requirements such as data entry, data updating and retrieving are included. Thus, this requirement is a high level requirement.

Requirement: A scheduling system to assign youths to properties. By: Rita Lester (External Systems Developer)

Importance : A scheduling system for Dig-it project could be a high level requirement. Transactions such as extracting a map or calendar showing the schedules would be involved. Therefore, a scheduling system is important to be a high level requirement.

Requirement: Find personal information of all staff and youths. By: Hugh Sterling (Service Centre Manager- S.E London)

Importance : In order to find personal information of all staff and youths, search criteria are needed to define over all records. This could include a set of functional transactions and therefore, it is a high level requirement.

Requirement: The system should allow tracking young people progress.

By: Peter Ellis (General Management)

Importance : Tracking young people progress could consist of logging information about young people, reviewing young people work assignments and assigning their progress. These set of actions make this requirement to be high level requirement.

Requirement: The system should be able to extract reports on attendance, group performance, the application of funds, etc.,

By: Hugh Sterling (Service Centre Manager- S.E London)

Importance : Extracting reports on attendance, group performance and the application of funds would include various transactions. This requirement must be a high level requirement.


COMP - 1648 Page 11

B 1.2.1 High Level Requirements that are hiding in the case study

In order to develop a perfect MIS system for Dig-it project, the high level requirements described in the workshop are not enough. Some critical high level requirements are still missing in the case study. Therefore, we would analyse the high level requirements that are hiding in the case study to be a complete system.

Manage Equipments

“Manage equipments” requirement is composed of adding new equipments, allocation of equipments and transportation of equipments. Thus, it is a high level functional requirement. Review Attendance

After a service to the garden of an elderly had been done, Tim (full time employee) will have to review the attendance of young people and volunteers. Review Attendance is a high level requirement. Review Attendance includes checking attendance, searching young people and volunteers, and assigning attendance. Plan Data Sharing

Data Sharing to Youth Action and third party organisation such as local authority might include a lot of processes. Functional requirements such as record necessary data for sharing, update the data, set recipient and sharing data might be included. Therefore, this requirement should be high level requirement.


COMP - 1648 Page 12

B 1.2.2 Complete High Level Requirements List

By combining high level requirements that we have found from the workshop and the case study, we get a complete high level requirements list for Dig-it project. The following high level requirements are critically important for Dig-it MIS system.

1. Manage Projects

First of all, MIS system must allow registering new project, managing existing projects and editing projects so that the system would be extendable for new projects rather than Dig-it project only.

2. Manage Data Entry

Manage Data Entry includes managing the registration of volunteers, permanent staff, participating youths and elderly. Updating and Retrieving of registered data are also included. This would be done by Tim (full time employee) according to the case study.

3. Operate Scheduling System

After managing data entry, the MIS system has to inform the teams about schedules. Operate scheduling system involves manage the team rotas, and match the teams for working to the gardens of the elderly, extracting map or calendar showing schedules and informing the teams.

4. Manage Equipments

After rotas and schedules had set up, Tim has to manage equipments. Manage equipments includes adding new equipments, allocation of equipments and transportation of equipments.


COMP - 1648 Page 13

5. Control Searching Process

Control searching process includes adding searching criteria, searching information and retrieving searched information. Updating and deleting searching criteria would also be involved.

6. Review Attendance

After a service to the garden of an elderly had been done, MIS shall need to allow review attendance. Review Attendance includes checking attendance, searching young people and volunteers, and assigning attendance of young people and volunteers.

7. Monitor Work Assignments

After calling round to the elderly people, Tim (full time employee) will monitor work assignments. Monitor work assignments includes set work assignments, set elderly people feedbacks in order to set group performance and young people progress.

8. Control Group Performance and Young People Progress

After a work assignment to the garden of the elderly had done, Tim will control group performance and young people progress. This consists of review elderly people feedbacks, assign group performance based on feedbacks, and assign young people progress based on feedbacks.

9. Extract reports on attendance, group performance, young people progress

Extract reports on attendance by reviewing attendance, and extract reports on group performance and young people progress by reviewing elderly people feedbacks.

10. Plan Data Sharing

Firstly, Youth Action needs to set data sharing policy to third parties. Functional requirements such as record necessary data for sharing, update the data, set recipient and sharing data would be included in plan data sharing.

Word Count for Part B1 - 1170


COMP - 1648 Page 14

B2. MoSCoW Prioritisation

B2.1 Updated High Level Requirement List with Priorities

No. High Level Requirement

Priority

1.

Manage Projects Must have


Must have


Must have


Should have


Could have

6.

Review Attendance Must have


Must have


Should have

9. Extract Reports on Attendance, Group Performance, Young People Progress

Could have


Won’t have


COMP - 1648 Page 15

B 2.2 Reasons in Setting Priorities

Requirement 1: Manage Projects

Priority: Must have

Reason : We cannot add new projects if we do not have this transaction. If we cannot register new projects, we could not make any further transaction. Therefore, manage project is a must have priority for MIS system.

Requirement 2: Manage Data Entry

Priority: Must have

Reason : Without data entry, we cannot do further business transactions. For example, without young people data, we cannot make young people rotas, searching process and tracking young people progress. Therefore, manage data entry is a must have priority for MIS system.

Requirement 3: Operate Scheduling System

Priority: Must have

Reason : As a minimal usable subset, the MIS system must have some way to manage volunteer rotas and match the teams to the gardens of the elderly. Without schedules, the teams would not know which gardens of the elderly they have to go and when they have to go. Consequently, the work assignments would not be done. Thus, operate scheduling system is a must have requirement.

Requirement 4: Manage Equipments

Priority: Should have

Reason : All the teams need equipments but this requirement is not so important that reports on attendance, group performance and young people progress could be extracted without this requirement. Therefore, it should be “should” have requirement.


COMP - 1648 Page 16

Requirement 5: Control Searching Process

Priority: Could have

Reason : The first incremental delivery of MIS system would not need searching process as there is small amount of data. The Dig-it project could operate well without searching process although it can be inconvenient.

Requirement 6: Review Attendance

Priority: Must have

Reason : Review attendance should be “must” have requirement. This is because without this requirement, we cannot produce reports on attendance.

Requirement 7: Monitor Work Assignments

Priority: Must have

Reason : Monitor work assignments is a must have requirement. This is because, without monitoring work assignments, we could not set elderly people feedbacks, group performance and young people progress. The minimal usable subset of the MIS system needs this requirement.

Requirement 8: Control Group Performance and Young People Progress

Priority: Should have

Reason : Control group performance and young people progress is very important but not critical requirement to include in the first incremental delivery. We can make this transaction in next incremental development. Setting elderly people feedbacks only is enough for the first incremental delivery of MIS system.


COMP - 1648 Page 17

Requirement 9: Extract Reports on Attendance, Group Performance, Young People Progress

Priority: Could have

Reason : We could implement reporting and statistics transactions in next incremental delivery. Therefore, we could defer reporting and statistics transactions in our first incremental delivery. Thus, extract reports on attendance, group performance, young people progress is “could have” requirement.

Requirement 10: Plan Data Sharing

Priority: Won’t have

Reason : Plan data sharing includes set data sharing policy, set recipient and share data. All these low level requirements are not directly related with Dig-it project. The project can operate very well without this requirement. The minimal usable MIS system could be done without this requirement.

Word Count for Part B 2.2 - 508


COMP - 1648 Page 18

B2.3 Time Boxing for the Project

We would plan time boxing for the project as part of DSDM approach. Time boxing is required so that Youth Action can give feedbacks on each time box for iterative development and the final product would be in line with the business needs. As a time box is an increment, we would deliver the product after each time box had finished.

As the management of Youth Action has targeted that the prototype system up and run within 4 months, we set the development duration of project to be finished within 4 months. 8 hours for a working day, 40 hours for a working week and 160 hours for a month. Therefore, the estimated project duration should be 640 hours for 4 months.


Hour Priority

1.

Manage Projects 60 Must have


70 Must have


80 Must have


40 Should have


50 Could have

6.

Review Attendance 50 Must have


60 Must have


60 Should have


70 Could have


60 Won’t have

Total hours – 600 hours

Must have - 320 hours (53% of total effort)

Should have- 100 hours (17% of total effort)

Could have- 120 hours (20% of total effort)

Won’t have – 60 hours (10% of total effort)


COMP - 1648 Page 19

First Timebox

In first timebox, we must include transactions which are vital in producing reports for Dig-it project, which is the main purpose of developing MIS system. Transactions such as review attendance and monitor work assignments are vital that reports on attendance, group performance and young people progress shall be produced using these transactions. Therefore, these transactions would be included in our first time box.


Hour Priority

1.

Manage Projects 60 Must have


70 Must have

6.

Review Attendance 50 Must have


60 Must have

Total hours for first time box 240

Second Timebox

By the second timebox, we must develop something that is useable and of importance. The main purpose of developing MIS system is to produce reports. Therefore, we would develop producing reports transaction in this timebox. Besides, transactions such as operate scheduling system and control group performance and young people progress are important that the delivered system would be inconvenient to use without this requirements.


Hour Priority


80 Must have


40 Should have


60 Should have


70 Could have

Total hours for second time box 250


COMP - 1648 Page 20

Third Timebox

Control searching process and plan data sharing would be developed in third timebox. We shall develop for good user interface and security in order to be a perfect system. After the iterative development of third timebox, the MIS system is considered to be ready to user.


Hour Priority


50 Could have


60 Won’t have

Total hours for third time box 110


COMP - 1648 Page 21

Section C- Legal, Social, Ethical and Professional Issues

C1. Management Summary for Obligations of the Data Controller

C1.1 Role of a Data Controller

According to Data Protection Act (1998), a data controller is a person who holds personal data of Data Subjects (for example- young people). Data controllers are kind of information commissioners who are responsible deal with data subject categories, data types, processing purposes and other parties to whom data is to be disclosed. The data controller has to follow the eight principles of DPA. DPA is in relation to protect data subjects from the misuse of their personal information.

Since Youth Action is a charity organisation and therefore it has to connect with third party companies and government authorities. Youth Action will have to share personal data of data subjects to these third parties. Data controllers in Youth Action are responsible to follow eight principles of DPA while sharing personal data. Otherwise, the whole charity would be legally harmed according to DPA.

The followings are the possible issues that the data controllers in Youth Action have to face while collecting and sharing personal data according to eight principles of DPA.

Fair

Example:” Youth Action needs health status of each young people to decide they can serve or not for gardens of the elderly. But some youths were not willing to share their health status. Therefore, Youth Action is going to collect their health status at the local hospitals without letting the young people know.”

According to DPA, personal data of data subjects must be obtained and processed fairly and lawfully. Collecting the health status of young people without letting them know is not fair and against the laws and regulations. Data controllers, for example- Tim (full time employee) and Sandra Lee (case worker) in Youth Action must inform the young people before they collect the data.


COMP - 1648 Page 22

Specific

Example: “Youth Action has the personal data of data subjects such as young people and volunteers. If government authorities or any third party organisation ask for the data, Youth Action will have to share them.”

Personal data must be shared only for specific lawfully purposes. Data controllers in Youth Action need to check why government authorities or third parties require personal data and what they intend to do with the data. Data controllers are also responsible to inform data subjects about data sharing and why third parties require their personal data.

Adequate

Example: “While collecting personal data of young people, Youth Action might ask for some irrelevant data such as race and religion.”

Data controllers in Youth Action must keep relevant data only, not excessive for specified purpose. Excessive personal data that are not required for specified purpose must be deleted. While sharing personal data to third parties, it is important not to be excessive than they actually required.

Accurate

Example: “The charity has recently been reprimanded for failing to keep personal data secure and, in some places, holding incorrect data.” (Page no.7 of 10, Youth Action Case Study)

The collected personal data (for example- name, address, age and gender of young people) must be accurate and up to date. Data controllers in Youth Action, for example- Tim (full time employee) and Sandra Lee (case worker), must endeavour for data accuracy. Otherwise, the data controllers have responsibility to face with consequences due to inaccurate data. Especially, the data controllers need to make sure whether the personal data are accurate or not before sharing to third parties such as local authority.


COMP - 1648 Page 23

Retention

Example:” Youth Action might still keep the personal data of young people who have already left volunteering the gardens of the elderly.”

Personal data of data subjects must be kept no longer than necessary for specific purpose. If there is no specific purpose, Youth Action must delete the personal data of young people who have already left from the charity.

Rights

Example: “Youth Action has the personal data of data subjects such as young people and volunteers. If government authorities or any third party organisation ask for the data, Youth Action will have to share them.”

Data controllers in Youth Action have to respect the rights of data subjects such as young people. If the data subjects are not willing to share their personal data to third parties, Data controllers should not share as possible. Otherwise, they have to compromise between third parties and data subjects. But, in some cases, data controllers must disclose personal data of data subjects to government such as local authority without compromising. Therefore, there is a big conflict of interest between the Data Protection Act (DPA) and Freedom of Information Act (FIA). In this case, data controllers in Youth Action have responsible to make decision whether disclose or not.

Security

Example:” The personal data and other confidential data might be unauthorized access or damaged by different ways.”

Data controller has to guarantee for the security of personal data. Technical and organisational measures for personal data are required to take against loss, damage and unlawful use in order to protect data subjects. Some technology would be required to protect the personal data. If the personal data of data subjects were damaged or used illegally, data subjects have their rights to sue data controllers and the Youth Action charity. Therefore, it is important to protect personal data securely. Otherwise, the Youth Action charity would be harmed.

Word Count for C1 - 850


COMP - 1648 Page 24

C2. Management Summary for Purpose of the BCS Code of Conduct

BCS code of conduct sets the professional standards required by the members as a condition of membership. Code is not a law but is a statement of shared commitments. The purpose of BCS code of conduct is to control IT professionals from misusing of IT knowledge and taking personal advantage. The code is exited also to protect the people who are lack of IT knowledge.

According to the following BCS code of conduct, we found three professional issues that might be occurred in Youth Action Charity deal with MIS system.

BCS Code of Conduct

The Public Interest

4.”Shall ensure that within professional field/s you have knowledge and understanding of relevant legislation, regulations and standards, and that you comply with such requirements.”

6.” Shall reject any offer of bribery or inducement.”

Example: Personal data of data subjects and other sensitive data of Youth Action have been delivered to DSDM developer in order to develop the MIS system. If other competitor charity of Youth Action or any third party would ask for those data, the DSDM developer might likely to share the data to them for personal advantage.

In this case, the DSDM developer would be in breach of rule 4 and 6 of the public interest of the BCS code of conduct. As a DSDM professional, he must not disclose sensitive data to third parties without letting the management of Youth Action know. Otherwise, he would be legally harmed according to existing laws and regulations. He must understand and follow the relevant legislation and regulations. And, he also must reject any offer of bribery or inducement to maintain the honour of being DSDM professional.


COMP - 1648 Page 25

Duty to Relevant Authority

9.”Shall not misrepresent or withhold information on the performance of products, systems or services, or take advantage of the lack of relevant knowledge or inexperience of others.”

Example: Since the management and other staffs in Youth Action are inexperience deal with system development, the DSDM developer might take advantage on this. For example, MIS system with system errors and insure functions might be developed. And, he may pretend that the system is error free and perfect.

In this situation, the DSDM professional would be in breach of 9 of duty to relevant authority of the BCS code of conduct. The DSDM developer must not misrepresent or withhold information on the performance of the system. The management of Youth Action also have the responsible to provide system requirements and security requirements vividly in the Service Level Agreement (SLA) with DSDM developer.

Professional Competence and Integrity

15.”Shall not claim any level of competence that you do not possess. You shall only offer to do work or provide a service that is within your professional competence.”

Example: The management of Youth Action might ask the DSDM developer to develop MIS system to be in line with the existing systems which were developed using different approaches. It is actually difficult to be reliable with existing systems. However, the DSDM developer may give promise to develop the MIS system to be reliable with the existing systems. Otherwise, he may lose his job.

The relevant clause would be rule 15 of professional competence and integrity of the BCS code of conduct. The DSDM developer must only offer to do work or provide a service that is within his professional competence. As a professional, He must not guarantee for something he cannot do. He must clearly identify what he could do and what he could not do to the management of Youth Action.

Word Count for Part C2- 591


COMP - 1648 Page 26

APPENDIX

Inappropriate Requirements List for High Level

Requirements from Rita Lester (External Systems Developer) Functional or Non-Functional Login Facility Functional A review system to allow staff and volunteers to oversee the programme.

Functional

Requirements from Hugh Sterling (Service Centre Manager) Functional or Non-Functional To extract a map or calendar, showing weekly schedules and work assignments

Functional

To find personal information of staff and youths Functional

The colour scheme of new system to match the colours used in the company logo, green and blue.

Non-Functional

Requirements from Peter Ellis (General Management) Functional or Non-Functional The system should be basis for new, company-wide system and should be highly extendable.

Non-Functional

The system should be personalisable (i.e. one person should be able to commission for an extra facility to the system, like a browser plug-in)

Non-Functional

To view reports on each branch to track performance and funds Functional

Requirements from Sandra Lee (Case Worker- S.E London) Functional or Non-Functional Registration of the elderly who need gardening services Functional

Registration of young people who are supplying services Functional

Young people to be assigned to the elderly for working in their gardens.

Functional

Track the assignments of young people and work schedule. Functional

Change detail information of people Functional

Send messages to people and log all communication Functional


COMP - 1648 Page 27

Requirements from Edward van Ryn (Volunteer) Functional or Non-Functional Searchable manuals and guides for new users

Non-Functional

To maintain searchable records of young people. Functional

Define search criteria over all records Functional

Requirements from Kevin Marsh (Case Work- North London) Functional or Non-Functional To track various projects at different branches.

Functional

To track what branch a particular youth is registered with Functional

The system must be fast, user friendly and error-free. Non-Functional

Software

Development Frameworks and Methods (University of Greenwich BIT Coursework) by Nay Linn Ko