This document provides details for the development of a new website for A Touch of Glass using the DSDM Atern framework. It includes:
- An introduction to the current A Touch of Glass business and reasons for a new system.
- An overview of the DSDM Atern framework and reasons it is suitable such as end user involvement, project size and timeline, quality focus, and communication.
- Advantages of DSDM Atern like timely delivery, early feedback, and prioritization of requirements.
- A list of high level and low level requirements for the new system along with MoSCoW prioritization of must, should, could, and would requirements.
- Discussion of legal,
Self-organization case study blinkist & zalando technologyTobias Leonhardt
Why we made it lighter: A case study of how to adopt self-organizing frameworks like holacracy, sociocray and enrich it with agile & lean principles as well as the integral theory. Real life examples from Blinkist and Zalando Technology
Human Resoruce - Training and development (GSK Glaxosmithkline India)←ครђเรђ Batra
It is basically a Training and Development report in which the critical analysis has been done and the methods used in the GSK GlaxoSmithKline and the survey questions
Trabalho desenvolvido para a disciplina de Comunicação Integrada de Marketing, da turma 01 de Marketing Digital da FGV Belo Horizonte.
Equipe:
Adriene Rezende
André Pierazoli
Camila Prazeres
Lucas Souto
Renata Sena
Yan Bueno
Enterprise Architecture in Strategy DeploymentJouko Poutanen
An industrial company implemented an enterprise architecture (EA) approach to better support its strategy deployment. The EA bridged the gap between the company's strategy and its implementation by formally describing the operational layer and mapping strategic goals to IT systems. This allowed the company to align its resources and capabilities with its operations strategy and market requirements. The EA identified "hot areas" where business value could be exploited through components like customer management and product delivery.
This document outlines a study that aims to develop a unified model of user acceptance of information technology. It begins with an abstract that reviews eight prominent existing models of user acceptance and discusses empirically comparing and combining their constructs. The study then describes empirically validating an integrated unified theory of acceptance and use of technology (UTAUT) model. It reviews the existing models and prior comparisons between models. The study then describes its empirical comparison of the eight models using data collected from various organizations, technologies, and time periods. The goal is to develop a unified model that integrates elements of the existing theories to better explain user acceptance.
The document discusses enterprise architecture governance. It introduces architecture governance and defines it as the core governing principles that help manage enterprise and IT architecture. These principles create processes to manage architecture functions and ensure alignment with risk, compliance, and regulatory standards. An architecture governance framework should establish governance committees, define artifacts like statements of work, and manage evaluation, selection, and implementation processes. The document outlines key activities an architecture governance framework should cover and provides examples of general best practices for implementation.
Ricardo Semler transformed his family's manufacturing company Semco through democratic and non-hierarchical organizational changes. He fired 60% of managers, cut salaries by 40% during an economic crisis but offered 39% profit sharing. Semler communicated change through one-page memos with headlines and enabled participation by rotating managers between functions with no fixed titles. He measured progress by having subordinates appraise managers and encouraged voluntary initiative with financial rewards. The transformations created a boundary-less and self-powered organization focused on employee empowerment, trust and removing bureaucracy.
This document discusses the Big Five personality traits model and its relevance to job performance in the banking sector. It focuses on the personality traits of an employee's direct supervisor based on the Big Five model, which includes Openness, Conscientiousness, Extraversion, Agreeableness, and Emotional Stability. Each of the supervisor's traits are described in detail. The document also explains how the supervisor's personality traits, as defined by the Big Five model, help him achieve targets at his workplace in the banking industry. Motivation is also discussed as a key driver of employee performance in banks.
Self-organization case study blinkist & zalando technologyTobias Leonhardt
Why we made it lighter: A case study of how to adopt self-organizing frameworks like holacracy, sociocray and enrich it with agile & lean principles as well as the integral theory. Real life examples from Blinkist and Zalando Technology
Human Resoruce - Training and development (GSK Glaxosmithkline India)←ครђเรђ Batra
It is basically a Training and Development report in which the critical analysis has been done and the methods used in the GSK GlaxoSmithKline and the survey questions
Trabalho desenvolvido para a disciplina de Comunicação Integrada de Marketing, da turma 01 de Marketing Digital da FGV Belo Horizonte.
Equipe:
Adriene Rezende
André Pierazoli
Camila Prazeres
Lucas Souto
Renata Sena
Yan Bueno
Enterprise Architecture in Strategy DeploymentJouko Poutanen
An industrial company implemented an enterprise architecture (EA) approach to better support its strategy deployment. The EA bridged the gap between the company's strategy and its implementation by formally describing the operational layer and mapping strategic goals to IT systems. This allowed the company to align its resources and capabilities with its operations strategy and market requirements. The EA identified "hot areas" where business value could be exploited through components like customer management and product delivery.
This document outlines a study that aims to develop a unified model of user acceptance of information technology. It begins with an abstract that reviews eight prominent existing models of user acceptance and discusses empirically comparing and combining their constructs. The study then describes empirically validating an integrated unified theory of acceptance and use of technology (UTAUT) model. It reviews the existing models and prior comparisons between models. The study then describes its empirical comparison of the eight models using data collected from various organizations, technologies, and time periods. The goal is to develop a unified model that integrates elements of the existing theories to better explain user acceptance.
The document discusses enterprise architecture governance. It introduces architecture governance and defines it as the core governing principles that help manage enterprise and IT architecture. These principles create processes to manage architecture functions and ensure alignment with risk, compliance, and regulatory standards. An architecture governance framework should establish governance committees, define artifacts like statements of work, and manage evaluation, selection, and implementation processes. The document outlines key activities an architecture governance framework should cover and provides examples of general best practices for implementation.
Ricardo Semler transformed his family's manufacturing company Semco through democratic and non-hierarchical organizational changes. He fired 60% of managers, cut salaries by 40% during an economic crisis but offered 39% profit sharing. Semler communicated change through one-page memos with headlines and enabled participation by rotating managers between functions with no fixed titles. He measured progress by having subordinates appraise managers and encouraged voluntary initiative with financial rewards. The transformations created a boundary-less and self-powered organization focused on employee empowerment, trust and removing bureaucracy.
This document discusses the Big Five personality traits model and its relevance to job performance in the banking sector. It focuses on the personality traits of an employee's direct supervisor based on the Big Five model, which includes Openness, Conscientiousness, Extraversion, Agreeableness, and Emotional Stability. Each of the supervisor's traits are described in detail. The document also explains how the supervisor's personality traits, as defined by the Big Five model, help him achieve targets at his workplace in the banking industry. Motivation is also discussed as a key driver of employee performance in banks.
Enterprise architecture is a discipline that helps define, develop, and exploit boundaryless information flow capabilities to achieve an organization's strategic goals. It translates business vision and strategy into effective enterprise change by developing principles and models that describe the future state and enable evolution. Common enterprise architecture frameworks include TOGAF, Zachman Framework, FEAF, and DODAF, which provide standardized approaches and classifications.
The document discusses extending the use of TOGAF (The Open Group Architecture Framework) beyond IT architecture to encompass enterprise architecture for the entire organization. It proposes two approaches: 1) Expanding the scope of TOGAF phases to focus on business, common, and detailed levels of the enterprise. 2) Extending TOGAF's capabilities by adapting phases for iterative assessment at any scope or complexity using time horizons, expanded Zachman framework, and agile principles. This allows TOGAF to address architecture for any part of the enterprise.
Effective Strategy Execution with Capability-Based Planning, Enterprise Arch...Iver Band
The difficulty of strategy execution should not be underestimated
Capability-based planning helps make strategy concrete
Enterprise architecture closes the remainder of this gap, and ensures alignment and coherence
Enterprise portfolio management allows managing large enterprise landscapes based on business value
ArchiMate models tie it all together, providing a clear line of sight from strategy definition to realization
Powerful tool support makes this a strong combination!
1) Amazon implemented Six Sigma methodology in 1999 as part of an operational excellence program led by Jeff Wilke to drive efficiencies.
2) Using Six Sigma tools like DMAIC and hiring Six Sigma Black Belts, Amazon reduced variation, waste, and improved inventory management, efficiency, and value stream control.
3) The impact of Six Sigma on Amazon was transforming it into a highly efficient global online retailer, increasing revenues manifold and allowing it to compete alongside technology giants like Apple and Microsoft.
Togaf – an overview of enterprise architectureKhawar Naseem
This document provides an overview of enterprise architecture (EA) and the TOGAF framework. It defines EA as the combination of business, technology, and strategy. The TOGAF framework helps organizations understand how business and technology resources align to support business goals and initiatives. It provides a holistic view of the organization's strategy, business, systems, and infrastructure and how they interrelate. The framework also helps prioritize initiatives and ensure the right projects are done in the right order.
This document discusses the relationship between enterprise architecture (EA) and project and portfolio management (PPM). It argues that EA and PPM have different but complementary perspectives in helping an organization translate strategy into realized value through portfolios and projects. The document provides examples of how EA and PPM can collaborate more effectively by having EA guide the enterprise towards its target state while PPM drives the enterprise strategically forward. It also provides a sample collaboration model where EA and the project manager work together on project architecture.
Taking team based decisions is a challenging task. It needs trust and a clever decision making framework to produce meaningful decisions with the best business outcomes, not a decision built on consensus. Each team member must then agree or disagree but commit to the decision taken. Only then do you achieve one team, one voice and effective team decision making.
In this keynote, Mischa Ramseyer and Pamela Hackett will propose a simple decision making framework to boost your team’s effectiveness, allow team members a voice, and ultimately, provide a tool to build the trust necessary for the right decisions to be made.
A simple guide to learn what EA is, why it’s important and how you can be using it to help your enterprise.
For more information: info@boc-group.com
Try ADOIT for EA:
https://www.boc-group.com/adoit/#test-it
Align, Inform, Inspire: Measuring Business Agility and SAFe® with Flow MetricsTasktop
During this on-demand webinar, Scaled Agile Principal Consultant and Framework team member, Andrew Sales, and Tasktop Sr. Value Stream Architect, Lee Reid, discuss how the three measurement domains of SAFe—Outcomes, Flow, and Competency—provide a comprehensive, yet simple, model for measuring business agility at every level of the enterprise and view data from an actual product value stream to demonstrate how Flow Metrics can enable productive conversations with the business about prioritizing work, while still maintaining the taxonomy of SAFe for teams to implement and improve.
Organize for Complexity, part I+II - Special Edition PaperNiels Pflaeging
The future of the Organization.
Special Edition of the BetaCodex Network´s white papers on Organizing for Complexity - two papers in one! Illustrations by Pia Steinmann
Taxonomy of change models slideshare 201703Mark Simpson
Having worked in change environments for many years and used a wide range of change models for many different types of change we found it useful to collate and categorise models for ease of reference. We have used four types of classification:
Contextual – broader strategic or macro models that can be helpful in understand a context of change, or support for change - Nadler and Tushman, congruence model being an example
High level change model – change specific models, but at a broader, sometimes even conceptual model - Carnall, change management model as an example
Actionable Model – detailed, with defined stages and actions, for example Accelerating Implementation Methodology (AIM) Change Management Methodology
Supporting – models that underpin our approach to change, they can apply to specific elements of change or help to understand certain elements, for example - Beckhard and Harris, change formula
Creating A Business Focussed Information Technology StrategyAlan McSweeney
This presentation describes a structured approach to creating a business-focussed information technology strategy.
An effective business-oriented IT strategy is an opportunity to resolve the disconnection and to ensure the IT function is able to and does respond to business needs and is trusted by the business to provide IT solutions.
The IT strategy will consist of static structural elements relating to the organisation of the IT function:
• Capabilities – skills and abilities the IT function should possess and be able to use effectively and efficiently
• IT Function Structure – the organisation and arrangement of the sub-functions and their responsibilities and relationships
• Operating Model – how the IT function work and delivers value and the processes it implements and operates
• Staffing And Roles – the numbers of people, their roles, responsibilities, expected skills, experience and abilities, workload, reporting structures and expected ways of operating
It will also include dynamic elements relating to initiatives, both enabling initiatives within the IT function and specific business initiatives required to achieve the business strategy.
This document provides an overview of enterprise architecture using TOGAF methodology. It includes numerous sample templates for business, data, application, and technology architecture segments. The key phases of TOGAF include developing baseline and target architectures for each segment, performing gap analyses, and defining roadmaps. Examples of sample templates are provided for elements like architecture visions, catalogs, matrices, diagrams, and gap analyses.
Shoe Corporation of Illinois Case Study -
President - Allison, and many more..
You can add about Product Development & customer involvement in product develeopment, ethical issues, etc
Development Framework method (Agile project analysis)MH Dip
This document contains an outline and sections for a report on developing a new system for Touch of Glass using DSDM. The outline includes sections on management summary, requirements, and legal/ethical issues. The summary discusses why DSDM is suitable, specifically that it allows delivering business value quickly in an agile manner to meet the organization's needs. Regular client reviews, timeboxing, and collaboration are identified as advantages. Potential drawbacks could include uncertainty from clients and lack of time impacting budgets. Section B provides details on functional and non-functional requirements identified through workshops.
Implementing Oracle E-Business suite for Tesla motor company .docxAASTHA76
< Implementing Oracle E-Business suite for Tesla motor company >
<PMGT 699-92- O-2019/Spring - Applied Project Management >
Prepared By
<Govind Rao Kurupathi>
<2/10/2019>
1. Executive Summary
1.1 ..Introduction………………………………………………………………………
1.2 .. Purpose………………………………………………………………………….
1.3 .. Scope……………………………………………………………………………
2. Project Overview
2.1Project Description
2.2Problem Statement
2.3Goals
2.4Project Background
2.5Product Objectives
2.6 ..Business Objectives……………………………………………………………..
2.7 ..Milestones……………………………………………………………………….
2.8Assumptions, Constraints and Dependencies
2.9Project Deliverables
2.10.. Project Success Criteria ………………………………………………………..
2.11..Schedule and Budget Summary
2.12..Evolution of the Plan
2.13..References
2.14Definitions and Acronyms
3. Stakeholder Register
4. Schedule
4.1 ..Purpose/Overview………………………………………………………………..
4.2 ..Schedule Baseline……………………………………………………………….
4.3 .. Schedule Control…………………………………………………………………
5. Resource Plan
5.1 .. Overview/Purpose of the Resource Section ……………………………………
5.2 ..Resourcing Strategy & Assumptions….………………………………………….
5.3 .. Resourcing Development………………………………………………………..
6. Risk Management Plan
6.1 .. Purpose/Overview………………………………………………………………
6.2 .. Risk Identification………………………………………………………………
6.3 ..Risk Analysis……………………………………………………………………
6.4 Risk Monitoring Plan …………………………………………………………….
7. Communications Plan
7.1..Overview
7.2..Communication Message and Delivery
7.3..Communications Guidelines
7.4.. Escalation Process
8. Procurement
9. Cost
9.1..Introduction
9.2.. Estimate Cost
9.3..Contingency reserve project purpose or justification
9.4..Budget
9.5..Project and Monitoring
9.6.. Project Reports
9.7..Cost Change Control
9.8..Project Budget
9.9..Microsoft Performance Report #1
9.10..Microsoft Performance Report #2
10. Integrated Change Control
1.Executive Summary Introduction
Tesla, Inc. is an American automotive and energy company based in Palo Alto, California. The company specializes in electric car manufacturing and, through its SolarCity subsidiary, solar panel manufacturing.
Real Tech Inc is an Oracle implementation specialist and an Oracle platinum partner. Tesla has awarded Real Tech Inc to implement the e-business suite of applications in its headquarters situated in Freemont, California. The suite of applications contains modules like Inventory management, Order management, Discrete manufacturing (Work In the process, Bills of materials) and financial modules (Accounts payable, receivable, Fixed assets and general ledger). The duration of the project is estimated to be 1 year (on the higher side). The team consists of 6 functional consultants, one database administrator, one Project Manager, one ERP practice head.
1.1 Purpose
The purpo.
The document describes the Dynamic System Development Method (DSDM) framework. It discusses DSDM's 9 principles, which include active user involvement, empowering teams to make decisions, and iterative and incremental development. It outlines the typical project structure in DSDM, including roles like project manager, team leader, and user ambassador. Projects follow a 7 phase process including feasibility study, business study, and iterative development phases. Core techniques recommended in DSDM are also described, such as timeboxing, prioritization rules, prototyping, and workshops.
The following document contains case study related to the startup my friend started, DIGITERIA.NET . Due to the changing nature of our startup, we moved to ERPAL, which is a web based ERP solution, ideal for small/medium enterprises.
Lead Allocation System - Attribute Driven Design (ADD)Amin Bandeali
The document describes applying Attribute-Driven Design (ADD) to design the architecture for a Lead Allocation System (LAS). It involves decomposing the system into elements, identifying architectural drivers from requirements, designing concepts to address the drivers, instantiating elements and defining interfaces. The security service element is decomposed in the second iteration to address authentication, authorization and integrity concerns using an Active Directory, user role database and gateway.
Development Frameworks and Methods Coursework (DFM CW)Aung Hein Htet
This document discusses the high level requirements and prioritization for a new B2C baby food delivery system called NutrarlyNow. It begins by listing some inappropriate requirements that are actually low or medium level before identifying 10 appropriate high level requirements. These include web browsing, customer management, meals creation, shopping basket, payment management, order management, internal messaging, delivery system management, feedback, and help section. The requirements are then prioritized using MoSCoW (Must have, Should have, Could have, Won't have). Customer management and meals creation are deemed must-haves while shopping basket, payment management, and others are lower priority. Reasons for each priority level are provided.
This project aims to develop a brick factory management system to help brick factory owners maintain their business activities. The system will store information such as brick categories, expenses, customers, purchases, raw materials, production, deliveries, payments and generate reports. It is being developed using HTML, CSS, JavaScript, Bootstrap, PHP and a MySQL database. Currently, maintaining factory records, communications and finances is difficult. The proposed system aims to simplify this through a basic web-based application.
Enterprise architecture is a discipline that helps define, develop, and exploit boundaryless information flow capabilities to achieve an organization's strategic goals. It translates business vision and strategy into effective enterprise change by developing principles and models that describe the future state and enable evolution. Common enterprise architecture frameworks include TOGAF, Zachman Framework, FEAF, and DODAF, which provide standardized approaches and classifications.
The document discusses extending the use of TOGAF (The Open Group Architecture Framework) beyond IT architecture to encompass enterprise architecture for the entire organization. It proposes two approaches: 1) Expanding the scope of TOGAF phases to focus on business, common, and detailed levels of the enterprise. 2) Extending TOGAF's capabilities by adapting phases for iterative assessment at any scope or complexity using time horizons, expanded Zachman framework, and agile principles. This allows TOGAF to address architecture for any part of the enterprise.
Effective Strategy Execution with Capability-Based Planning, Enterprise Arch...Iver Band
The difficulty of strategy execution should not be underestimated
Capability-based planning helps make strategy concrete
Enterprise architecture closes the remainder of this gap, and ensures alignment and coherence
Enterprise portfolio management allows managing large enterprise landscapes based on business value
ArchiMate models tie it all together, providing a clear line of sight from strategy definition to realization
Powerful tool support makes this a strong combination!
1) Amazon implemented Six Sigma methodology in 1999 as part of an operational excellence program led by Jeff Wilke to drive efficiencies.
2) Using Six Sigma tools like DMAIC and hiring Six Sigma Black Belts, Amazon reduced variation, waste, and improved inventory management, efficiency, and value stream control.
3) The impact of Six Sigma on Amazon was transforming it into a highly efficient global online retailer, increasing revenues manifold and allowing it to compete alongside technology giants like Apple and Microsoft.
Togaf – an overview of enterprise architectureKhawar Naseem
This document provides an overview of enterprise architecture (EA) and the TOGAF framework. It defines EA as the combination of business, technology, and strategy. The TOGAF framework helps organizations understand how business and technology resources align to support business goals and initiatives. It provides a holistic view of the organization's strategy, business, systems, and infrastructure and how they interrelate. The framework also helps prioritize initiatives and ensure the right projects are done in the right order.
This document discusses the relationship between enterprise architecture (EA) and project and portfolio management (PPM). It argues that EA and PPM have different but complementary perspectives in helping an organization translate strategy into realized value through portfolios and projects. The document provides examples of how EA and PPM can collaborate more effectively by having EA guide the enterprise towards its target state while PPM drives the enterprise strategically forward. It also provides a sample collaboration model where EA and the project manager work together on project architecture.
Taking team based decisions is a challenging task. It needs trust and a clever decision making framework to produce meaningful decisions with the best business outcomes, not a decision built on consensus. Each team member must then agree or disagree but commit to the decision taken. Only then do you achieve one team, one voice and effective team decision making.
In this keynote, Mischa Ramseyer and Pamela Hackett will propose a simple decision making framework to boost your team’s effectiveness, allow team members a voice, and ultimately, provide a tool to build the trust necessary for the right decisions to be made.
A simple guide to learn what EA is, why it’s important and how you can be using it to help your enterprise.
For more information: info@boc-group.com
Try ADOIT for EA:
https://www.boc-group.com/adoit/#test-it
Align, Inform, Inspire: Measuring Business Agility and SAFe® with Flow MetricsTasktop
During this on-demand webinar, Scaled Agile Principal Consultant and Framework team member, Andrew Sales, and Tasktop Sr. Value Stream Architect, Lee Reid, discuss how the three measurement domains of SAFe—Outcomes, Flow, and Competency—provide a comprehensive, yet simple, model for measuring business agility at every level of the enterprise and view data from an actual product value stream to demonstrate how Flow Metrics can enable productive conversations with the business about prioritizing work, while still maintaining the taxonomy of SAFe for teams to implement and improve.
Organize for Complexity, part I+II - Special Edition PaperNiels Pflaeging
The future of the Organization.
Special Edition of the BetaCodex Network´s white papers on Organizing for Complexity - two papers in one! Illustrations by Pia Steinmann
Taxonomy of change models slideshare 201703Mark Simpson
Having worked in change environments for many years and used a wide range of change models for many different types of change we found it useful to collate and categorise models for ease of reference. We have used four types of classification:
Contextual – broader strategic or macro models that can be helpful in understand a context of change, or support for change - Nadler and Tushman, congruence model being an example
High level change model – change specific models, but at a broader, sometimes even conceptual model - Carnall, change management model as an example
Actionable Model – detailed, with defined stages and actions, for example Accelerating Implementation Methodology (AIM) Change Management Methodology
Supporting – models that underpin our approach to change, they can apply to specific elements of change or help to understand certain elements, for example - Beckhard and Harris, change formula
Creating A Business Focussed Information Technology StrategyAlan McSweeney
This presentation describes a structured approach to creating a business-focussed information technology strategy.
An effective business-oriented IT strategy is an opportunity to resolve the disconnection and to ensure the IT function is able to and does respond to business needs and is trusted by the business to provide IT solutions.
The IT strategy will consist of static structural elements relating to the organisation of the IT function:
• Capabilities – skills and abilities the IT function should possess and be able to use effectively and efficiently
• IT Function Structure – the organisation and arrangement of the sub-functions and their responsibilities and relationships
• Operating Model – how the IT function work and delivers value and the processes it implements and operates
• Staffing And Roles – the numbers of people, their roles, responsibilities, expected skills, experience and abilities, workload, reporting structures and expected ways of operating
It will also include dynamic elements relating to initiatives, both enabling initiatives within the IT function and specific business initiatives required to achieve the business strategy.
This document provides an overview of enterprise architecture using TOGAF methodology. It includes numerous sample templates for business, data, application, and technology architecture segments. The key phases of TOGAF include developing baseline and target architectures for each segment, performing gap analyses, and defining roadmaps. Examples of sample templates are provided for elements like architecture visions, catalogs, matrices, diagrams, and gap analyses.
Shoe Corporation of Illinois Case Study -
President - Allison, and many more..
You can add about Product Development & customer involvement in product develeopment, ethical issues, etc
Development Framework method (Agile project analysis)MH Dip
This document contains an outline and sections for a report on developing a new system for Touch of Glass using DSDM. The outline includes sections on management summary, requirements, and legal/ethical issues. The summary discusses why DSDM is suitable, specifically that it allows delivering business value quickly in an agile manner to meet the organization's needs. Regular client reviews, timeboxing, and collaboration are identified as advantages. Potential drawbacks could include uncertainty from clients and lack of time impacting budgets. Section B provides details on functional and non-functional requirements identified through workshops.
Implementing Oracle E-Business suite for Tesla motor company .docxAASTHA76
< Implementing Oracle E-Business suite for Tesla motor company >
<PMGT 699-92- O-2019/Spring - Applied Project Management >
Prepared By
<Govind Rao Kurupathi>
<2/10/2019>
1. Executive Summary
1.1 ..Introduction………………………………………………………………………
1.2 .. Purpose………………………………………………………………………….
1.3 .. Scope……………………………………………………………………………
2. Project Overview
2.1Project Description
2.2Problem Statement
2.3Goals
2.4Project Background
2.5Product Objectives
2.6 ..Business Objectives……………………………………………………………..
2.7 ..Milestones……………………………………………………………………….
2.8Assumptions, Constraints and Dependencies
2.9Project Deliverables
2.10.. Project Success Criteria ………………………………………………………..
2.11..Schedule and Budget Summary
2.12..Evolution of the Plan
2.13..References
2.14Definitions and Acronyms
3. Stakeholder Register
4. Schedule
4.1 ..Purpose/Overview………………………………………………………………..
4.2 ..Schedule Baseline……………………………………………………………….
4.3 .. Schedule Control…………………………………………………………………
5. Resource Plan
5.1 .. Overview/Purpose of the Resource Section ……………………………………
5.2 ..Resourcing Strategy & Assumptions….………………………………………….
5.3 .. Resourcing Development………………………………………………………..
6. Risk Management Plan
6.1 .. Purpose/Overview………………………………………………………………
6.2 .. Risk Identification………………………………………………………………
6.3 ..Risk Analysis……………………………………………………………………
6.4 Risk Monitoring Plan …………………………………………………………….
7. Communications Plan
7.1..Overview
7.2..Communication Message and Delivery
7.3..Communications Guidelines
7.4.. Escalation Process
8. Procurement
9. Cost
9.1..Introduction
9.2.. Estimate Cost
9.3..Contingency reserve project purpose or justification
9.4..Budget
9.5..Project and Monitoring
9.6.. Project Reports
9.7..Cost Change Control
9.8..Project Budget
9.9..Microsoft Performance Report #1
9.10..Microsoft Performance Report #2
10. Integrated Change Control
1.Executive Summary Introduction
Tesla, Inc. is an American automotive and energy company based in Palo Alto, California. The company specializes in electric car manufacturing and, through its SolarCity subsidiary, solar panel manufacturing.
Real Tech Inc is an Oracle implementation specialist and an Oracle platinum partner. Tesla has awarded Real Tech Inc to implement the e-business suite of applications in its headquarters situated in Freemont, California. The suite of applications contains modules like Inventory management, Order management, Discrete manufacturing (Work In the process, Bills of materials) and financial modules (Accounts payable, receivable, Fixed assets and general ledger). The duration of the project is estimated to be 1 year (on the higher side). The team consists of 6 functional consultants, one database administrator, one Project Manager, one ERP practice head.
1.1 Purpose
The purpo.
The document describes the Dynamic System Development Method (DSDM) framework. It discusses DSDM's 9 principles, which include active user involvement, empowering teams to make decisions, and iterative and incremental development. It outlines the typical project structure in DSDM, including roles like project manager, team leader, and user ambassador. Projects follow a 7 phase process including feasibility study, business study, and iterative development phases. Core techniques recommended in DSDM are also described, such as timeboxing, prioritization rules, prototyping, and workshops.
The following document contains case study related to the startup my friend started, DIGITERIA.NET . Due to the changing nature of our startup, we moved to ERPAL, which is a web based ERP solution, ideal for small/medium enterprises.
Lead Allocation System - Attribute Driven Design (ADD)Amin Bandeali
The document describes applying Attribute-Driven Design (ADD) to design the architecture for a Lead Allocation System (LAS). It involves decomposing the system into elements, identifying architectural drivers from requirements, designing concepts to address the drivers, instantiating elements and defining interfaces. The security service element is decomposed in the second iteration to address authentication, authorization and integrity concerns using an Active Directory, user role database and gateway.
Development Frameworks and Methods Coursework (DFM CW)Aung Hein Htet
This document discusses the high level requirements and prioritization for a new B2C baby food delivery system called NutrarlyNow. It begins by listing some inappropriate requirements that are actually low or medium level before identifying 10 appropriate high level requirements. These include web browsing, customer management, meals creation, shopping basket, payment management, order management, internal messaging, delivery system management, feedback, and help section. The requirements are then prioritized using MoSCoW (Must have, Should have, Could have, Won't have). Customer management and meals creation are deemed must-haves while shopping basket, payment management, and others are lower priority. Reasons for each priority level are provided.
This project aims to develop a brick factory management system to help brick factory owners maintain their business activities. The system will store information such as brick categories, expenses, customers, purchases, raw materials, production, deliveries, payments and generate reports. It is being developed using HTML, CSS, JavaScript, Bootstrap, PHP and a MySQL database. Currently, maintaining factory records, communications and finances is difficult. The proposed system aims to simplify this through a basic web-based application.
Increase productivity and improve the predictability of software projects. Interest in the Scrum Agile process framework is exploding as companies discover that Scrum enables them to manage software projects with greater reliability and improve responsiveness to customers. This class introduces the skills that project managers and team leaders need to perform the basic steps of a Scrum process for software development.
-Learn how Scrum practices relate to project management fundamentals
-Learn the essentials of Scrum as a software development process
-Learn the three Scrum roles, three Scrum meetings, and three Scrum artifacts
-Project Managers and team leads learn basic planning, tracking, and management skills
-Product Managers learn how to develop and prioritize requirements
-Team members learn how to estimate and break down work
This document contains a summary and details of Pravin Gurav's professional experience as a Software Test Engineer. He has over 4 years of experience in testing web applications using Selenium with Java and TestNG frameworks. He is proficient in test automation, regression testing, defect management and has experience working with tools like Jenkins, JIRA and databases like Oracle. The document lists his education qualifications and provides details of several projects he has worked on related to testing software applications and upgrades.
Lecture 19,20 Software Development Process Models.pptxSeniorUsama
The document discusses three software development process models: the Waterfall model, Prototyping model, and Rapid Application Development (RAD) model. The Waterfall model involves dividing the development process into separate sequential phases. The Prototyping model involves iteratively developing prototypes based on customer feedback. The RAD model involves developing components in parallel on a time-boxed basis and assembling them into a working prototype.
The document is a software requirements specification (SRS) for a new online booking system for Cool Ski Resorts. It provides an overview of the project, outlines the system features and user requirements. Key aspects include: allowing customers to book rooms, equipment and classes online; managing inventory, payments and financial reports; and improving work efficiency for staff. The system is intended to digitize current paper-based processes and provide a better experience for customers.
This document discusses requirements analysis and prioritization for a new home sector order processing system for the Clean Brite Company (CBC). It begins by providing background on CBC and issues with a previous failed IT project. A requirements workshop was then held with various CBC departments to gather requirements. 18 initial requirements were listed, but some were deemed "non-appropriate high level requirements" as they were not functional or specific enough. The document identifies 11 "high level requirements" that are critical for the new system. It concludes by explaining MoSCoW prioritization for categorizing requirements as "Must have", "Should have", "Could have", or "Won't have".
The document provides an overview of the waterfall model and agile methodologies for software development projects. It discusses:
- The linear sequential phases of the waterfall model and when it is suitable.
- Issues with the waterfall model like inability to handle changes and lack of testing throughout.
- Benefits of agile like ability to adapt to changes, early delivery of working software, and improved success rates.
- Key aspects of the Scrum agile framework like sprints, daily stand-ups, and product backlogs.
- Differences in how development costs are treated as capital expenditures or operating expenses between waterfall, agile, and cloud-based models.
The document discusses requirements for a new system called Alive being developed by Walk2Live (W2L) to manage its health and fitness franchise business. Section A provides a management summary of W2L and the need for the new Alive system. It analyzes whether the Dynamic Systems Development Method (DSDM) would be suitable for the Alive system. Section B discusses high level requirements for the system and prioritizes them using MoSCoW techniques. It identifies some inappropriate requirements that are not essential. Section C covers legal, social, ethical and professional issues to consider.
Perspectives on the adherance to scrum rules in software project managementnooriasukmaningtyas
Adapting users need to fulfill their requirements and delivering products to be on time within the planned cost, is critical matter that all software project managers (SPM) put the highest priority for it while considering the users satisfaction at the same time. Agile methodology is one of the solutions provided by software engineers (SE), to get the customers involved in the system development life cycle (SDLC) to avoid the risk nonconformance cost. Yet SPM’s still facing the nonconformance costs and the dynamic changes, and the root cause of the issue is not pointed on to find a solution for it. This undertaking research aimed at determining whether software developers understand scrum rules. In addition, how does this knowledge gab affect the software projects success from the project management perspective. Furthermore, the engagement studied the impact of lack of enough knowledge on the topic to project delivery. The collected data from the qualitative and quantitative methods, which was conducted with scrum teams who worked in the health information system (HIS), Educational solutions, and Governmental solutions has showed deviations in organizational practices and team conflicting, competition, and pressure as well as declined product quality.
The document discusses various aspects of the design process for interactive systems, including design rules, usability engineering, and iterative design. It provides an overview of different types of design rules such as principles, standards, and guidelines. Specific examples of design rules like learnability, flexibility, and robustness are mentioned. Ben Shneiderman's eight golden rules of interface design are also summarized, which include consistency, informative feedback, error handling, and reducing memory load.
Alecia Chrin is a senior program/project manager with over 11 years of experience managing enterprise projects involving healthcare, financial, insurance, government, and regulatory compliance projects. She has experience with Java-based web development projects. She manages projects using both Agile and SDLC methodologies. She stays up to date on the latest technologies and ensures requirements are clearly captured and communicated to stakeholders and developers through tools like email, MS Project, and Visio process maps. She has experience across the full project lifecycle from strategic planning to deployment.
Presentation by sathish nataraj sundararajanPMI_IREP_TP
This document discusses process excellence for new age project management. It describes tools like Advanced Product Quality Planning (APQP), target cost matching, target cost approach curve, point of no return (PONR), ABC analysis, and characteristic management that can be used to enhance the planning, steering, and reporting of projects. These tools help structure project management by aiding in planning, tracking project timelines and costs against targets, prioritizing parts, and ensuring all requirements are met. Using such tools in a standardized way across a company brings transparency and helps complete projects on time and on budget.
Similar to Development frameworks and methods (20)
Communicating effectively and consistently with students can help them feel at ease during their learning experience and provide the instructor with a communication trail to track the course's progress. This workshop will take you through constructing an engaging course container to facilitate effective communication.
LAND USE LAND COVER AND NDVI OF MIRZAPUR DISTRICT, UPRAHUL
This Dissertation explores the particular circumstances of Mirzapur, a region located in the
core of India. Mirzapur, with its varied terrains and abundant biodiversity, offers an optimal
environment for investigating the changes in vegetation cover dynamics. Our study utilizes
advanced technologies such as GIS (Geographic Information Systems) and Remote sensing to
analyze the transformations that have taken place over the course of a decade.
The complex relationship between human activities and the environment has been the focus
of extensive research and worry. As the global community grapples with swift urbanization,
population expansion, and economic progress, the effects on natural ecosystems are becoming
more evident. A crucial element of this impact is the alteration of vegetation cover, which plays a
significant role in maintaining the ecological equilibrium of our planet.Land serves as the foundation for all human activities and provides the necessary materials for
these activities. As the most crucial natural resource, its utilization by humans results in different
'Land uses,' which are determined by both human activities and the physical characteristics of the
land.
The utilization of land is impacted by human needs and environmental factors. In countries
like India, rapid population growth and the emphasis on extensive resource exploitation can lead
to significant land degradation, adversely affecting the region's land cover.
Therefore, human intervention has significantly influenced land use patterns over many
centuries, evolving its structure over time and space. In the present era, these changes have
accelerated due to factors such as agriculture and urbanization. Information regarding land use and
cover is essential for various planning and management tasks related to the Earth's surface,
providing crucial environmental data for scientific, resource management, policy purposes, and
diverse human activities.
Accurate understanding of land use and cover is imperative for the development planning
of any area. Consequently, a wide range of professionals, including earth system scientists, land
and water managers, and urban planners, are interested in obtaining data on land use and cover
changes, conversion trends, and other related patterns. The spatial dimensions of land use and
cover support policymakers and scientists in making well-informed decisions, as alterations in
these patterns indicate shifts in economic and social conditions. Monitoring such changes with the
help of Advanced technologies like Remote Sensing and Geographic Information Systems is
crucial for coordinated efforts across different administrative levels. Advanced technologies like
Remote Sensing and Geographic Information Systems
9
Changes in vegetation cover refer to variations in the distribution, composition, and overall
structure of plant communities across different temporal and spatial scales. These changes can
occur natural.
How to Setup Warehouse & Location in Odoo 17 InventoryCeline George
In this slide, we'll explore how to set up warehouses and locations in Odoo 17 Inventory. This will help us manage our stock effectively, track inventory levels, and streamline warehouse operations.
Strategies for Effective Upskilling is a presentation by Chinwendu Peace in a Your Skill Boost Masterclass organisation by the Excellence Foundation for South Sudan on 08th and 09th June 2024 from 1 PM to 3 PM on each day.
How to Make a Field Mandatory in Odoo 17Celine George
In Odoo, making a field required can be done through both Python code and XML views. When you set the required attribute to True in Python code, it makes the field required across all views where it's used. Conversely, when you set the required attribute in XML views, it makes the field required only in the context of that particular view.
RHEOLOGY Physical pharmaceutics-II notes for B.pharm 4th sem students
Development frameworks and methods
1. COMP 1648 : Development Frameworks and Methods
Due Date : 22/11/2017
School Name : KMD (Yangon, Myanmar)
Coursework Title : The Touch of Glass
Total Word Count : 3964
Table of Content
2. 1. Management Summary 3
1.1 Introduction of current A Touch of Glass business 3
1.2 Introduction of DSDM Atern 4
1.3 Reason for Using DSDM Atern for TOG 4
1.3.1 End User Involvement 4
1.3.2 Size of Project 4
1.3.3 Delivery on Time 4
1.3.4 Never Compromise on Quality 5
1.3.5 Communicate Continuously and Clearly 5
1.4 Advantages of DSDM Atern 5
1.4.1 Delivery on Time 5
1.4.2 Receive User Feedback Early 5
1.4.3 Gives visibility of working prototypes early 5
1.4.4 Requirement Prioritisation 5
1.5 Disadvantages of DSDM Atern 6
1.5.1 Documentation is complex 6
2. High Level requirements analysis and MoSCow prioritisation 6
2.1 Low Level Requirement 6
2.1.1 Security 6
2.1.1.1 Register and Log In 6
2.1.1.2 Payment for the item 6
2.1.1.3 Hosting 6
2.1.2 Performance 7
2.1.2.1 The website load quickly 7
2.1.3 Usability 7
2.1.3.1 Look and feel of the website 7
2.1.3.2 Rotating 3D views of the products 7
2.1.3.3 Add to Cart 7
2.1.3.4 Feedback 7
2.1.3.5 Register a URL 7
2.1.3.6 Contact Us 7
2.1.3.7 Shipping method 8
2.1.3.8 Return item if customer unlike 8
2.2 High Level Requirement 8
2.2.1 Showcase the product 8
2.2.2 Search and browse different products 8
2.2.3 Communicate with customers who order bespoke item 8
2.2.4 Sign up for tours of the facilities 8
2.2.5 Sign up for glassblowing classes 8
2.2.6 Notify the item to manufacture 9
2.2.7 Allow to create own design 9
3. 2.2.8 Gather statistics on item popularity 9
2.2.9 Report Sales and market by graphs and figures 9
2.3 High Level Requirement with MoSCow 9
2.3.1 MoSCow Prioritisation List 9
2.3.2 Must Have Requirement 10
2.3.3 Should Have Requirement 10
2.3.4 Could Have Requirement 11
2.3.5 Would Have Requirement 11
3. Legal, Social, Ethical and Professional issues 11
3.1 Role of the Data Controller 11
3.2 Legal, Social, Ethical and Professional Issues 12
3.2.1 Copyright for Website 12
3.2.2 Get customer data 12
3.2.3 Email Spamming 12
3.3 BCS Code of Conduct 13
3.3.1 Public Interest 13
3.3.2 Professional Competence and Integrity 13
3.3.3 Duty to Relevant Authority 13
3.3.4 Duty to the Profession 13
4. Reference 14
1. Management Summary
1.1 Introduction of current A Touch of Glass business
A Touch of Glass is the company of selling glassware, ornaments and sculptures
including bespoke pieces, glasses and vases. Currently, the company using peer-to-peer e-
Commerce website and this website just including a few function such searching and browsing
item, add to cart and payment. And then, the company communicating with customers via third
party systems such as social media and facing some issues, mainly at customer care.
The company owner, Sarah decided to build the new system to solve their issues and
she would like to add tours of the facility, the business allow the seeing of manufacturing
4. process. So, the new systems support both e-commerce, scheduling classes and tours and also
solve the issues they are facing.
1.2 Introduction of DSDM Atern
I decided to use Agile for development of the system of TOG because agile is based on
highly participation of customer from the beginning of the system started. Agile allows the
customer to test the system in every step of development lifecycle. So, the user can save
money and time and also get the product that meets all of their’s requirements. There have a lot
of methodologies are follow in Agile such as XP, Scrum, ASD, Crystal, DSDM and FDD.
Among I would like to use DSDM Atern for development of the system. DSDM (Dynamic
Systems Development Method) is the longest-established Agile method and “mainly operated in
the corporate environment where it consistently demonstrates its ability to successfully work
with and complement existing corporate processes”. The latest version of DSDM, Atern
incorporates those improvements.
1.3 Reason for Using DSDM Atern for TOG
The Owner, Sarah Bromley want to get a prototype system up within 3 months and allow
the old system for flawless replacement.
1.3.1 End User Involvement
DSDM Atern need to participate End-User in all of the incremental processes and the
almost staff of the TOG are very keen to participate because all of the staffs believe that current
system is the challenge to make the effectively market promotions and manage customer care.
The owner also expand her business.
1.3.2 Size of Project
DSDM Atern suggest that the team size is optimum is seven +/- two people. We make
the first meeting in Sarah(Owner), Thomas(Packing and Shipping), Frederic Smith(Operations),
Willow Grant(Customer care and Social Media), Mary(Accounts), Sean Sterling(Glassblower)
and me in Meeting Room A. So, there have eight people to discuss the requirement and that is
suitable to use DSDM Atern for project.
1.3.3 Delivery on Time
Delivery on Time is the one of principle of DSDM Atern and advance planning of
timeboxes and setting the timeframe. The dates of timeframe are never change because
features are depending on business priorities to achieve the deadline. The project have to show
prototype within 3 months and that is suitable to use DSDM Atern.
5. 1.3.4 Never Compromise on Quality
The project must be tested early and continuously and review constantly, that is one of
the principle of DSDM Atern. The company said that “ the system should allow for flawless
replacement of the current system”. Using DSDM Atern, the user can test the project and review
during the development of project. So, at the end of 3 months, they will get the project that meet
all of the requirement.
1.3.5 Communicate Continuously and Clearly
DSDM Atern uses facilitated workshops, daily standups, modeling, prototyping,
presentations and encourage informal face-to-face communication. That will get good
relationship with customer and early get their requirement.
1.4 Advantages of DSDM Atern
1.4.1 Delivery on Time
DSDM frequently deliver of results to make the ensure of detected error and easily
reversed and knew the source of error. These process are both on program code and document
like requirements or data models. So, the project can deliver the right time.
1.4.2 Receive User Feedback Early
DSDM Atern deliver the progress of project to user and user can see the status of
project and easily give the feedback of doing project. That can get benefit both user and
developer. The developer can also know the error early. That will help to quickly move the
progress of project status.
1.4.3 Gives visibility of working prototypes early
DSDM Atern deliver the project when every function would be done. So, the user can
visible the project early and if the user would not like it, they will change early and will save
money and time of doing project.
1.4.4 Requirement Prioritisation
DSDM Atern prioritise the function using Moscow prioritisation. Moscow stand for must
have, should have, could have and Would have this time. The priorities are set before the
workshop commences are under continual review. Must have and should have functions are
usually deliver 80% of the business requirement.
6. 1.5 Disadvantages of DSDM Atern
1.5.1 Documentation is complex
DSDM Atern make a lot of workshop and meeting and also daily informal face-to-face
communication. So, this need a lot of documentation to record each meeting and workshop.
Citation
"Quotium | Comparison of Key Methodologies in AGILE."
http://www.quotium.com/performance/comparison-of-key-methodologies-in-agile/.
"Introduction to DSDM Atern."
http://www.methodsandtools.com/archive/dsdmatern.php.
2. High Level requirements analysis and MoSCow
prioritisation
2.1 Low Level Requirement
The requirements listed in Appendix A are also included low level requirements. The
following are the low level requirement and classified with security, performance and usability.
2.1.1 Security
2.1.1.1 Register and Log In
Customer, as well as new users who did not have account in website must be access
the website and some function such as search and browse different products whether they are
log in or not. The own products of company are not important data. According to modern
marketing, most of website are show their products and allow to access most of function without
logging in.
2.1.1.2 Payment for the item
Payment for the item is the very important function for customers and company. It is
need to secure and do carefull and can be done later after the prototyping. This function is not
the main function for prototyping.
2.1.1.3 Hosting
Uploading Backend code and database on server are not necessary for prototyping.
7. 2.1.2 Performance
2.1.2.1 The website load quickly
The performance of website speed is not important for prototyping. It can be done later
after finished and tested the main function.
2.1.3 Usability
2.1.3.1 Look and feel of the website
The user interface of website is not the high level requirement for the prototype. It can be
done later after finished and tested the main function.
2.1.3.2 Rotating 3D views of the products
Showing the products is the functional requirement but rotating of 3D views of the
products is not the high level requirement. And then 3D views of technique is difficult to make
and it need time and manpower. So, this function is not available within 3 months.
2.1.3.3 Add to Cart
Sometime customers want to collect the item they interested and then they choose again
the item they collected and buy item within it. This function related stock function and it is the
non functional requirement for prototype system.
2.1.3.4 Feedback
Some customers want to give feedback for using the systems and it is not need at
prototype system.
2.1.3.5 Register a URL
Register a URL and get a domain name for access the website by everyone is not the
high level requirement for prototyping.
2.1.3.6 Contact Us
Contact us is important for customer care. Some customers want to know about items,
tours and classes and they will ask the company. But this function is not main function and it
can be done later before prototyping.
8. 2.1.3.7 Shipping method
This function relate with delivery and this function need to do specify the location and
this function will happen after the payment for the item. So, this function is not high level
requirement for prototyping.
2.1.3.8 Return item if customer unlike
The company allow the return item if customer are not unlike the design or quality. This
function is about customer care and this function is not important function for prototyping. This
function can be done later.
2.2 High Level Requirement
2.2.1 Showcase the product
Showcasing the product is the main function of this website. Any user can freely visit and
view the product of TOG.
2.2.2 Search and browse different products
Searching item with item name or price or any information is very important for business
website. There is no patient customer to search item by scrolling. All customer want to search
by some filters.
2.2.3 Communicate with customers who order bespoke item
One of the function of this company is that the customer can order bespoke item and if
the customer order bespoke item, the customer and the company will need to speak for
ordering. The chat will be included messages and sending pictures.
2.2.4 Sign up for tours of the facilities
The company want to expand their business and the company allow to customers who
are interested to watch how to manufacturing glassware. So, the website allow the customers to
view the tours informations. But the customers will need to sign up to get the tours informations.
2.2.5 Sign up for glassblowing classes
The company plan to open the classes to teach glassblowing and the customers will get
the informations of available classes. But the customers will need to sign up to get the classes
informations.
9. 2.2.6 Notify the item to manufacture
This function is very important for all staff in company. The glassblower can easily know
when the customer order the item and the packing and shipping staff can also get the
information about order via using the system. That can reduce workload.
2.2.7 Allow to create own design
The company want to allow the customer to create their own design and they can order
their created design. The function is including drawing and import some image.
2.2.8 Gather statistics on item popularity
This function is very important for marketing and promotion. Nowadays, every websites
and app are trace the customer who using their app which items are interested by whom, which
items are selling a lot in recently and so on. According to statistics information, The company
can make marketing and promotion.
2.2.9 Report Sales and market by graphs and figures
Reporting is very important for every company. Every company want to know how many
item are sold out and which items are left in stock. If the company make the business plan by
reviewing the report. Nowadays, reporting are made up of graphs, pipe chart and so on.
2.3 High Level Requirement with MoSCow
After analysing high level requirement, MoSCow prioritisation is carried out in the below
diagram.
2.3.1 MoSCow Prioritisation List
Priority Type Requirement
Must Showcase the product
Must Communicate with customer who order bespoke item
Must Search and browse different products
Must Notify the item to manufacture
Should Sign up for tours of the facilities
Should Sign up for glassblowing classes
Could Allow to create own design
10. Would Gather statistics on item popularity
Would Report Sales and market by graphs and figures
2.3.2 Must Have Requirement
Requirement : Showcase the product
Reason : Showing the product is the most important function in this website. The only reason of
customer visiting the website is to view the product. So, the showcase the product and give the
product information to customer is the “Must Have” function for this website.
Requirement : Communicate with customer who order bespoke item
Reason : One of the service of TOG is making the bespoke item. The company want to allow
the customer to get this service via the website. So, there is need to speak about item between
customer and company. The website must allow to private chat between company and
customer who order bespoken item. This private chat allow messaging and sending picture.
Requirement : Search and browse different products
Reason : There is no patient customer to scrolling website to get their wanted item. All customer
want to search with some filter such as product name, price, latest upload, most popular and so
on. There is no website does not get search and browse function. So, search and browse
different products is the “Must Have” function for this website.
Requirement : Notify the item to manufacture
Reason : The system notifies the glassblower and packing and shipping staff when there is get
the order from customer. If the system cannot notify them the system admin or glassblower and
packing and shipping staff will ask informal. This happen to increase workload. Notify the item to
manufacture is the “Must Have” function for this website.
2.3.3 Should Have Requirement
Requirement : Sign up for tours of the facilities
Reason : The company is planning to expand the business by allowing customer to visit the
manufacturing process. So, the website can access enrollment of tours of the facilities and this
“Should Have” requirement for this website.
Requirement : Sign up for glassblowing classes
11. Reason : The company is planning to expand the business and open the classes that are teach
glassblowing. So, the customer who would like to teach the glassblowing can enroll the classes
via the website and this “Should Have” requirement for this website.
2.3.4 Could Have Requirement
Requirement : Allow to create own design
Reason : One of the company service is that the company allow the customer to order their own
design and the customer can make the design via the website. But this function has a lot of
technical challenge to available create the design. This function have to make like a drawing
tool and it take time and give a lot of manpower. So, this function is third priority high
requirement of the website.
2.3.5 Would Have Requirement
Requirement : Gather statistics on item popularity
Reason : This function is very important for marketing and promotion. But this function cannot
make without “Must Have” and “Should Have” function. This function can make when finishing
“Must Have” and “Should Have” function. So, Gather statistics on item popularity is the “Would
Have” requirement for this website.
Requirement : Report Sales and market by graphs and figures
Reason : This function is very important for high level management( Owner). But this function
cannot make without “Must Have” and “Should Have” function. This function can make when
finishing “Must Have” and “Should Have” function. So, report sales and market by graphs and
figures is the “Would Have” requirement for this website.
3. Legal, Social, Ethical and Professional issues
3.1 Role of the Data Controller
TOG make the own website and need to store the company’s important data and user
information. The company need to consider Data Protection Act. The Act protect the personal
data and the Act say “Personal Data” as “data which relate to a living individual who can be
identified from those data or from those data and other information which is in the possession
of, or is likely to come into the possession of, the data controller, and includes any expression of
opinion about the individual and any indication of the intentions of the data controller or any
other person in respect of the individual” said in "Key definitions of the Data Protection Act | ICO."
12. For example, the customer fill the information for shipping process, the system will know the
customer location, credit card number and so on. There data can only be updated by customer and only
access to know these customer information by system admin. If the system admin resign or quit the job
the system denies to access that admin. The company also should include Terms and Condition of data
protection in job appointment letter.
Citation
"Key definitions of the Data Protection Act | ICO." https://ico.org.uk/for-organisations/guide-to-data-
protection/key-definitions/.
3.2 Legal, Social, Ethical and Professional Issues
3.2.1 Copyright for Website
Copyright is required for TOG, especially the content such as ornaments and sculptures,
including bespoke pieces, as well as functional items such as glasses and vases. Copyright law
protect the stealing from company data by any unauthorised person. TOG have to register the
copyright.
3.2.2 Get customer data
The website include payment system and the system store customer credit card number
or other important things of customer. There is possible issues that is the internal staff get these
data and tell other people and that is unethical. So, the customer data must be secure and only
authorised person such as owner can only access these data.
3.2.3 Email Spamming
Nowadays, spamming the email account of customer is the popular approach of
marketing strategy. But this is not unethical. The website must to ask customer to send
promotion news or and other emails. If the customer would not like to receive the email, the
website will not send promotion emails.
Example for copyright for website
If the TOG register the copyright, the TOG can sue by law when any people (individuals
or organisation) used the information from TOG without getting permission from TOG. By
registering the copyright, the company can protect their information.
Example for Get customer Data
When customer knew their information stolen from website, the customer can sue the
company. If the customer sue the company, the company image will damage and will get the
punishment from the court. So, the company need to check the user level of using system.
Example for Email Spamming
13. Email Spamming is the one of the approach of marketing. Many company send their
promotion to customer email. But it can annoy for customer and that is unethical. If the website
want to send any information the website firstly ask the permission from customer. And also
there has option setting for disable and enable setting of email spamming in the website.
3.3 BCS Code of Conduct
The British Computer Society (BCS) set the responsibility rules and professional
standards for the behaviour of profession. BCS code of conduct describe the disciplinary action
which can result in expulsion from membership.
There have four section in BCS Code of Conduct. They are public interest, professional
competence and integrity, duty to relevant authority and duty to the profession.
3.3.1 Public Interest
A professional have due to regard for privacy and security of customer and company
intellectual properties. A professional conduct their work discrimination of sex, marital status,
sexual orientation, nationality, race, colour, religion, age or any other condition or requirement.
3.3.2 Professional Competence and Integrity
A profession never claim any level of competence that they do not have. A professional
must be reject the offer of unethical inducement. And a profession can only accept the work or
service within his/her professional competence. A profession should not get any level of
competence that his/her does not possess.
3.3.3 Duty to Relevant Authority
A professional must be take the responsibility of work impacts and his colleagues
working under his supervision. A professional should not disclose or give authorise to disclose
to use confidential information of customer or company for personal benefit. A professional
should not be take advantage of the lack of relevant knowledge. A professional should be avoid
any situation to get the conflict about interest between relevant authority.
3.3.4 Duty to the Profession
A professional developer should maintain the good relationship between colleagues,
supervisor or client. A professional should take any job to uphold the reputation of the
profession and should not accept any job to disrepute the profession. A professional should
seek the improve of professional skill by participating the organisation. A professional should
support the follower to improve their professional development.
Citation
14. "Code of Conduct for BCS Members (2011) | Ethics Codes Collection." 23 Feb. 2012,
http://ethics.iit.edu/ecodes/node/5248.
"Code of conduct | Membership | BCS - The Chartered Institute for IT."
http://www.bcs.org/category/6030.
4. Reference
"Quotium | Comparison of Key Methodologies in AGILE."
http://www.quotium.com/performance/comparison-of-key-methodologies-in-agile/.
"Introduction to DSDM Atern."
http://www.methodsandtools.com/archive/dsdmatern.php.
"Key definitions of the Data Protection Act | ICO." https://ico.org.uk/for-organisations/guide-to-
data-protection/key-definitions/.
"Code of Conduct for BCS Members (2011) | Ethics Codes Collection." 23 Feb. 2012,
http://ethics.iit.edu/ecodes/node/5248.
"Code of conduct | Membership | BCS - The Chartered Institute for IT."
http://www.bcs.org/category/6030.