+1443 776-2705 panelessays@gmail.com

takeholder Requirements 

What are the requirements of the application? 

Will various modules be developed? 

What are the dependencies? 

Will system be required to interact with external system resources? For example, databases.  

What guidelines must be followed to ensure that system requirements are met? 

Discuss Cost and Quality 

Based on system design requirements how will cost be affected? 

Does the features set based on the design requirement require multiple modules 

Business Process 

How will the design streamline business process? 

Are there redundant processes? 

How will streamlining processes affect cost? 

Are there design considerations for future upgrade? 

System Architecture Aligned with System Requirements

System Architecture is a very important aspect of the system life cycle. Based on results from your group discussion and other information gathering, complete a document showing the Architectural Design of the application to be developed. 

Some key factors to include:

How the system will streamline the business process. 

Stakeholders' requirements. 

Cost, features, and quality. 

APA references and intext citations attachment is project up to date

Running head: BUSINESS CASE REPORT

BUSINESS CASE REPORT 16

Business Case

Connie Farris

Robert Whisehunt

Colorado Technical University

IT Capstone I

(IT487-1904A-01)

Maria Thomas

Business Case

Contents Unit 1: 3 Overview of Company and Client Business Case 3 Introduction 3 Expertise 3 Solutions 3 Unit 2 5 Application Requirement Elicitation Strategy 5 Trade-off Analysis 5 Milestones and Due Dates 7 Unit 3 9 System Components and Design Requirements TBD 9 Unit 4 10 Methodology for Application Development Process TBD 10 Unit 5 11 Complete Features and Trade-off Analysis TBD 11 Unit 6 12 Milestones and Deliverables based on Date and Dependencies TBD 12 Unit 7 13 System Architecture Aligned with System Requirements TBD 13 Unit 8 14 Technical Design Document TBD 14 Unit 9 15 Design Review Checklist TBD 15 Unit 10 16 Testing and Deployment TBD 16 References 17

Unit 1:

Overview of Company and Client Business Case

Introduction

The business case we have chosen is a customer service application for a jewelry store called Unique Creations. We will design on online architecture for them at the request of the owner who would like a modern up to date Network Architecture that will enable them to better serve the customers and communicate with existing vendors and to expand search for material need for Unique Creations. They use platinum, titanium, gold, silver and stainless steel for all the custom and original jewelry pieces. They also have plans to open a few more businesses soon.

Expertise

Choctaw Innovations has worked in the IT realm for over 3 years they work in with many different methodologies in order to do their best work. Holding a CMMI score of level 3 conducing relatively working to improve themselves for success. Our company has the expertise to provide Unique Creations with the requirements desired for this Network Architecture.

Solutions

The goal will be to develop the appropriate network, the key to these goals will depend on the network structure implemented with reliability and security design for this company with the ability to expand and grow in the future and cost effective. The main objective of this design is to provide the very best practice for implementing a secure network. We also need to develop a time frame and budget analysis. The solution to this is to ensure that the network architecture will perform as expected and meet the needs of the stakeholder. We will consider a cloud based along with the LAN. In conclusion, requirements management streamline its phase using the capability maturity model integration (CMMI) to blend and define best practices throughout the process. Various set of practices are defined by CMMI and they support to improve the quality of a system. Both approaches define proper processes for eliciting, analyzing, specifying and validating requirements.

Unit 2

Application Requirement Elicitation Strategy

Trade-off Analysis

Selection of features

Organizations have realized the need to optimize their customer service applications, in order to enhance their success. One of the key strategies to achieving optimal customer service application is to reduce the features included by removing the irrelevant ones. Exploding the system with massive data from varying features will make it hard to analyze and extract relevant information for decision making. The users of the application will also find it hard to use, owing to the complexity resulting from the irrelevant features. The selection process will apply genetic algorithm and immune clone algorithm to eliminate redundant and irrelevant features, which can also reduce accuracy and speed of the system (Mistrík, 2016). The features that will be eliminated include those that are duplicated, noisy and irrelevant ones.

Selection of features is one of the complex and problematic issue in achieving optimal customer service application. Elimination of the redundant and irrelevant features will enable the developer to enhance efficiency of the application. Optimal feature selection will enable increased accuracy and speed of the application. It will also ensure increased relevance of the data collected, which will be easier to analyze for decision making.

Cost of modification

Although modification of the features will add costs associated with the product development, it will optimize its efficiency. The gains associated with the feature modification should exceed the costs associated with the same. However, the product design should maximize on the effectiveness of the features, in order to reduce modification costs. Relevant information should be integrated in the design process. Some of the strategies that may be used to enhance the process include prototyping and concept genesis (Chipman, 2014).

Project Timeframe

Planning is an essential element in implementation of projects. Time schedule guides a project manager to plan for various activities of the projects in their respective durations, in order to complete within the right timeframe. The planning phase should analyze relevant information in order to achieve an accurate time schedule. The developer should foresee potential risks, which may disrupt the smooth flow of the activities. Modification of the features should be planned for and allocated resources and time (Burke, 2019). Consequently, although modification of the features will escalate the duration of the project, it will be adequately planned for in the initial stages. Every task in the design will be allocated start and end time, with clearly outlined milestones. Modification of features will enable the developer to align the application with the user requirements.

User requirements

Achievement of the project deliverables will heavily rely on the effectiveness in planning and design. Every task within the project should be planned for and allocated adequate time and resources. Achievement of the user requirement will imply success of the project. Consequently the planning of the project will entail establishment of tasks, dates of tasks, duration, and dependencies. Some techniques that will be useful include Gantt chart and Chronology chart, which will ensure a clear and systematic flow of activities of the project.

Milestones and Due Dates

Milestones and due dates will enable effective planning of the project, which will ensure smooth flow of the activities. The process of planning will require identification of the tasks and milestones, in order to plan for their dependencies.

Dependencies

The relationships among the activities and tasks of the project will determine dependencies and their implementation order. The project tasks have various types of dependencies, including finish-to-start, and start-to-start. The dependencies will be clearly outlined through Gantt chart, which will effectively outline start and end times for every task. The planning start will start following finish of information gathering and analysis. The information will be used in planning for the design and establishment of the duration for every task. Implementation of the design application will follow finish of prototyping and testing the prototype (Davis, 2013). Additionally, development of the features will be implemented simultaneously for different features. Modification of the features will start after finishing testing of the application and establishment of its shortcomings.

Simultaneous operations

The tasks that do not have hard dependencies will be implemented simultaneously, in order to reduce the project duration. Data collection from various sources and their individual analysis will be performed simultaneously. Design of various features of the application will also be performed in parallel. Development of the designed features may also run simultaneously. The critical path method will determine the sequence of activities in the order in which they will be performed. The longest path will determine the project duration. The parallel activities which do not have hard dependencies will be performed simultaneously (Busch, 2016). 

Effectiveness of the Approach

The approach will enhance the quality of the product, since it will improve on the management of the project. Critical path method allows the project management to identify the critical activities, which are supposed to be given special attention. The approach will reduce on the duration of the project, since it will clearly determine dependencies of various tasks and their timelines. Additionally, the approach will provide an opportunity to compare actual and planned progress, which will further ensure fast tracking of the activities.

User requirements

The requirements of the user will be met effectively through application of the approach. The approach will provide an opportunity for the project management to enhance its planning and decision making. The critical path method will help in identifying the critical activities, which significantly affect achievement of the project objectives. The project duration will be significantly being reduced to meet the user’s requirement by establishing the sequence of the activities and their relationships. Additionally, the approach allows for graphical representation of the overall project, which will further enhance effective and smooth flow of the operations (Noble, 2014).

Unit 3

System Components and Design Requirements TBD

Unit 4

Methodology for Application Development Process TBD

Unit 5

Complete Features and Trade-off Analysis TBD

Unit 6

Milestones and Deliverables based on Date and Dependencies TBD

Unit 7

System Architecture Aligned with System Requirements TBD

Unit 8

Technical Design Document TBD

Unit 9

Design Review Checklist TBD

Unit 10

Testing and Deployment TBD

References

Bennatan, E.M. (2017) On time within budget: Software project management and techniques. New York: Wiley services. Information Systems,53,1-15

Burke, R. (2019). Project management techniques. Place of publication not identified: Burke Publishing.

Busch, D. H. (2016). The new critical path method: The state-of-the-art in project modelling and time reserve management. Chicago, Illinois: Probus.

Top of Form

Chipman, M. L., & United States. (2014). Toward an improved FIPS cost-benefit methodology: Phase II, descriptive models–general purpose application software development and maintenance. Gaithersburg, MD: U.S. Dept. of Commerce, National Bureau of Standards.

Bottom of Form

Top of Form

Davis, E. W. (2013). Project management: Techniques, applications, and managerial issues. Norcross, GA: Industrial Engineering & Management Press, Institute of Industrial Engineers.

In Mistrík, I., In Soley, R. M., In Ali, N., In Grundy, J., & In Tekinerdogan, B. (2016). Software quality assurance: In large scale and complex software-intensive systems.

Bottom of Form

Top of Form

In Noble, C., In Griffin, A., & In Durmusoglu, S. (2014). Open innovation: New product development essentials from the PDMA.

Top of Form

Top of Form

Bottom of Form

Bottom of Form

Bottom of Form