Systems Analysis and Design Report: HP Autonomy Case Study Analysis

This report delves into the core concepts of systems analysis and design, critically evaluating the strengths and weaknesses of both traditional and agile methodologies. It explores four variations of agile methodologies, addressing transition challenges faced by organizations moving from traditional to agile approaches. The report includes a feasibility study for a business-related problem at HP Autonomy, focusing on the Meister-task project, covering technical, operational, and economic feasibility. It outlines user and system requirements, potential constraints, and tools used for system investigation. The analysis extends to functional system design aspects, such as interface, program, and database design. The report provides a comprehensive analysis of system design, emphasizing the practical application of methodologies to solve business problems. It includes hardware and software requirements for Meister-task and its external standing.

Systems Analysis & Design

Table of Contents
INTRODUCTION...........................................................................................................................3
MAIN BODY ..................................................................................................................................3
Critically evaluate the strengths and weaknesses of the traditional and agile system's analysis
methodologies.............................................................................................................................3
Discuss about four variations of agile methodologies and transition problems faced by
organizations that move from the traditional to the agile approach............................................5
Produce a feasibility study for a system for a business related problem of HP Autonomy........6
Technical feasibility of Meister-task project:.............................................................................7
User and system requirements and any constraints, including possible security issues, tools
and techniques used to investigate the systems...........................................................................9
Analyse a system using a suitable methodology for a business-related problem.....................10
Functional system help for designing approaches such as interface design, program design and
database design for system.......................................................................................................12
CONCLUSION..............................................................................................................................15
REFERENCES..............................................................................................................................16

INTRODUCTION
System analysis design is a sequential procedure which used for organization to perform
different operations and functions in proper manner. This report will discuss about the strength
and weakness of traditional or agile system that analyzing the methodologies. Furthermore, this
assignment will describe the different variations occurs in the agile methodologies and what are
the problem faced by organization to move from other approaches. It will discuss about the User
and system requirement which possible to include the tools, techniques and issues investigate the
overall system. However, this report will describe the feasibility study for the system that can use
in the business process. This assignment will analyze the system by using the suitable
methodology for the purpose business related problems and issues.
MAIN BODY
Critically evaluate the strengths and weaknesses of the traditional and agile system's analysis
methodologies
Traditional development Life cycle analysis methodology:
Traditional development life cycle is important concept that used in the organization to
transform the newly development project into the operational one. This process is mainly used to
provide the framework in both non technical and technical activities. It also delivered the best
quality of system which meets to business goals and objectives (Adnan and Ritzhaupt, 2018).
This methodology follows the sequential process for analyzing the overall planning for project
management software. There are some important steps for using the traditional life cycle
methodology.
 Planning
 System Analysis and requirements
 System Design
 Development
 integration and testing
 Implementation Operations and maintenance

Strength of traditional methodology:
 The strength of this method have ability to manage a large projects and maintain the
quality assurances.
 It is based on the long term scalability. Traditional development life cycle method depends on the assumptions that user easily
understand the requirements and it has not changed the significantly at the time of
development process.
Weaknesses of traditional methodology:
 It may be seen many problems faced by user and does not see the overall solution until
the system is not completed in proper ways.
 It is expensive and more time consuming. In this way, it is difficult for user to review the
intermediate products.
Agile System analysis methodology:
Agile methodology is basically used an iterative and term based approach which helps for
project management software. It is quickly delivered the application with the complete functional
components (Alvarez and et.al., 2018). It is the formulation that solve the problem and issues
that generated during task management. This system is including the different models such as
prototyping, object oriented analysis and design etc.
Strength of agile Methodology:
 Agile methodology is the rapid development cycle which end with the different
incremental delivery of software pieces.
 It is highly flexible in terms of development to adopt a new concept and minimize the
waste of resources and time. This methodology is continuously maintained the quality assurance and testing project
management software.
Weakness of Agile Methodology:
 It arises the problem occurs with the flow of coordination.
 It is difficult for planning at the early stages.
 A Lack of long term planning may be increased the disorganizing the cases. In this way,
project may end up off track.

Discuss about four variations of agile methodologies and transition problems faced by
organizations that move from the traditional to the agile approach
Being a System analyst, it is necessary for managing the project management software
through agile method because it is based on the scrum technique to handle the overall
functionality of software. There are four different type of variations in the agile methodology as
following:
Extreme programming (XP)- It is a unique among the agile method that surveyed
because it concerns about the software development. It follows the principle's series that analyst
should follows.
Dynamic system development (DSDM)- It is the oldest recognize frame work which
applicable in the rapid application development. This method is applicable in the software
development and provide the best quality of product to their consumer DSDM is interlocking set
of processes each of them is iterative and incremental.
Crystal methods – Developer and analyst may use this method for collecting all
requirement which are needed for interaction with the other. It is mainly focused towards the
communication for managing the business task in proper manner (Benveniste and et.al., 2018). It
is integrated with optimize team and other unique project to run on the different platforms. This
method is developed the product such as game and other cooperative.
Scrum- Scrum is mainly uses on the basis of monthly "Sprints." this type of sprints has
to developing features and also collecting the backlog. It also checks the team members and
identify the progress of projects.
Transition challenges
There are some Challenges occurs in transition methodology so that developer can move
to agile methodologies for software development. Communication challenge- It is important part of project development whereas it would
be generating communication barriers between software team and managers. In HP,
developer can move to the agile methodology because it is the fastest process to maintain
the quality. It also helps for improving the product quality development. This
methodology is being chosen by the manager where they can improve the communication
and collaboration.

 Project management role – The traditional software development practices whose values
are completely in contrast with the agile methodology. It helps for project manager to
focus towards planning. They also supporting the team members towards the growth and
development (Biondi, Buttazzo and Bertogna, 2018). The role of developer is to facilitate
towards the project but as they were adopted a new methodologies and support the self
organization. It is shifted and move to the agile methodology for reducing the issues and
problem in project.
 Documentation- Developers are trying to implement the agile methodologies, but it is
great challenges in terms of maintenance of project development. In this way, developer
can move traditional method to agile method. Agile scrum is possible to handle the
complex situation which is the best in terms of poor maintenance. Many people are
preferred to chose the new and existing technology for project management software
development.
Produce a feasibility study for a system for a business related problem of HP Autonomy
Feasibility study is mainly defined the practical extent to which a project can be
performed different operations and functions. It is considered the important point that
accomplish the requirements is practical and workable in software project (Chapman, 2018).
There are some information required such as resource availability, cost estimation, benefits of
software development for HP. It is established the main reason for developing the software.
There are some common point considered in the feasibility study such as technicals feasibility,
economic feasibility and operational feasibility.
Feasibility study is important aspects for the software project because it provides the
proper direction to implement the logical things. It should contain the primary data, price and
logical thoughts. HP is mainly focused towards their specific goals and objectives. It is required
for Meister task project to analyse the entire contribution, practically materialized in terms of
organisation (John and Raju, 2018). The outcome should be depended on the feasibility of
product whereas how it can applicable in the business operations and functions. Meister task is a
type of web system project that help for organisation to manage and control their business plans.
It is required for business process because it offers various type of feature which essential for
team management of HP firm.

Features of Meister-task:
 Role and permission- it assigns the different role of team members and restrict to
modify the project and their task.
 User group- it would be creating group of different users within the business. It will
share the project them at one click. Project team- It makes sure that the project visible to the entire business. Each and every
members are actively collaborated on the specific project such as Meister-task. They are
joined together to create business plans which allows for different team administrator.
Technical feasibility of Meister-task project:
Technical Feasibility- It assesses the current resource and technology which help for
accomplish the need of user in the software within appropriate budget or time (Kirlik, 2018). In
HP, Software development team is mainly focused towards the Meister-task project because it
can perform different task to provide the information in proper manner.
This type of feasibility is important of business process because it gives the brief idea
about the design and implementation process. It depends on the software and hardware
requirement that easily maintained their functionality and operations in proper manner.
Technical details:
Hardware requirement:
 Monitor resolution 1024 x 758 and higher
 Windows XP / 98 /7
 2 GB RAM
 internet connection broad band services
 Keyboard Microsoft mouse and other compatible pointing device.
Software requirement:
 MS Office
 Java programming language
 Power point viewer Adobe Acrobat Reader
Estimating cost- This project software is reliable because it offers variety of free
packages for business. The organization is trying to take unlimited plans and using for the

purpose of business management. The cost of business plan is $8.25 user/ month. User can use
the different features such as unlimited integration, workflow automation, Up to 250MB file
attachments, searchable task archive and statics or reports etc.
Estimating operation and Support - This software is performing various type of
operations and support the other features to share information from one place to another. It may a
good idea for organization to use the concept for managing the lack of functionality. Sometimes,
it is less expensive than other to provide the appropriate solutions. It supports the different task
of organization.
Information quality- This software system is maintained the quality of information
which acquired all the relevant details to share from one system to another. It is a straight
forward software that combine with the different features and capabilities to manage the project
in proper manner (Maylawati, Darmalaksana and Ramdhani, 2018). This software is applicable
for task manageable into the unified platform. It is predefined custom fields that automatically
appear with each project task.
External standing- Meister-task project is simply used the agile methodology for
performing different task in proper manner. It will create a project to assign task for each and
every members. Meister task is flexible project that adopt the work flow and make everyone in
the same pages. It is integrated with the mindmiester, online mind mapping that start to
brainstorm with the other real time or create project plan visually.
Operational Feasibility-
It assesses the extent to which needs software to perform different operations for solving
a business problem and user need. It depends on the resources and involvement of visualizing
whether the software will operate properly or not. Developer involves to install the software and
operates in properly. Operational feasibility is performed different tasks.
 It determines whether the problem anticipated in the user requirement which highly
priority.
 Analyze whether the user can adopt a new software for growth and development. Determines whether the solution suggested by the software development team is
acceptable.
Economic Feasibility-

It determines whether the need of software is capable of gathering the financial gain of
HP Firm. It includes the actual cost of software development team, software and hardware etc. It
is necessary for software team to consider the expense and activity need to carry out the software
development (Nuzzo and et.al., 2018). It is required for developer to consider the benefit of
meister-task project in the business process of HP. Initially, it can check the economically
feasible for the organization.
 Cost incurred on the software development to produce the long terms benefits for
organization
 It is required a cost to conduct the fully perform software and also investigate.
 It is also considered the cost of software, hardware equipment and training to the
development team.
User and system requirements and any constraints, including possible security issues, tools and
techniques used to investigate the systems
Meister-task is the best tool for the business purpose to perform different functions
according to the need and requirement. It is used in the organization to manage the task of
mobile and web system. It is the powerful collaboration with full feature, flexible etc. Software
team will use this tool to manage all the project type in proper manner. It keeps maintain the up
to date information to progress (Oinas-Kukkonen and Harjumaa, 2018). It is more than simple
task management where all the project related information is safely store in proper manner. It is
accessible for team members to get insights into the own ways to increase the productivity and
profitability.
User requirement specification
The user requirement specification is mainly described the enterprise need what the user
require from the system. User requirement is initial process of validation, before system is
created (Oinas-Kukkonen and Harjumaa, 2018). Afterward, it is needed to test the entire system
and quality performance through user acceptance testing. It is usually a planning documents
which created when acquiring a system and trying to identify the specific needs.
 Home Screen accept all the information about the production such as project name, date
and number.
 It is continuously print data on the screen through printer.
 It should be included the scope of system and their specific objective for the project.

 The overall functions and flows must be performed in proper manner.
 The entire system should be maintained by the development team.
System requirement Specification-
System requirements are necessary for developer to use the best platform to build a
design. It can use the meister-task tool to manage the functionality of business. System
requirement is divided into different ways functional and non functional requirement. A
functional need specify the something when the user need to perform task such as print the
estimation cost (Reddy and Miravete 2018). On the other hand, non- functional requirement
specify the requirement which not covered in proper ways. There are different points considered
in system requirement as following:
 Accessibility
 Compliance's
 Accuracy
 Backup and restore
 Dependency on third parties
 management of configuration
 Compatibility of software, database and standards.
Analyse a system using a suitable methodology for a business-related problem.
An agile methodology relies upon the iterative completion and incremental goals for
business with specific team management. It is mainly represented as a process that sequentially
collecting and gathering the relevant information regarding the design the software and build a
final product (Singh and Kaur, 2019). HP is basically moved towards the decision making
approach as the knowledge and skill require for employees. Agile technique is used for the
project management to handle the business task in efficient manner.
On the other hand, Scrum is a specific methodology whereas agile technique that focused
on the empowerment and iterative delivery of product. Designers are concerned about the
product where they design user friendly system and easy maintenance(Singh and Kaur, 2019).
Agile methodology is segmenting the business processing cycle of solving the problem in the
form of chunks. In this way, HP firm is adapting the methodology to handle the business
operations and functions. Design- Create an efficient system with build in tests to expose the gap of execution.

 Share- it is widely shared the discovery process and solutions. Develop- designer is continuously builds a team to solve the problem and also identifying
the capabilities.
 Improve- team members are investigated the system need and requirement. Afterwards,
solving the business issues.
Agile companies are continuously influx the technology as they start to evolved the new things
in the business process. HP is the firm that adopt this technique to manage their software
development task effectively. They can use digital documentation, communication and data
management (Singh and Kaur, 2019). This is possible when the firm increase the documentation
management solution which allows for employee to use the digital concept to secure their
information. In this way, it also connects with the other enterprise It enables them to crate out the
process and taking the control what is done and how.
Cost control of project is another factor and agile technique project management help for
manager to control the system through dynamic ways. It could happen by allows to make new
change quickly with less cost.
Apply Agile methodology to business problem and solving:
There are lack of technology and communication created a problem in the business
operations. It makes sure that designer to start new things and also share their new vision with
the flexibility to make it reality. Agile methodology is a basically applicable in the project
management software to increase the capabilities and abilities (Singh and Kaur, 2019). In
business process, This technique is offering the practical aspects to deliver the project according
to their requirement. Customer satisfaction is main part of business so that manager is trying to
control, manage and identify the risk by using tools. Designer need to able to manage everyday
tasks and challenges.
Agile methodology is finding business problem and issues to solve them.
 Ensuring the high quality of products and services
 Increased the customer satisfaction
 Increase and manage the project control
 taking the less risk on the projects

Functional system help for designing approaches such as interface design, program design and
database design for system
Functional system is a type of approach which determine that how the entire software
designing in properly working. It is needed for designer used the functional system that help for
managing the business operations and functions in proper manner. There are some important
approaches considered in the functional system.
Il
lustration 1: Flow Chart