Running head: SYSTEM ACQUISITION
1
The System Acquisitions Strategy
Brandon Whitley
South University Online
ITS4090
December 8, 2015
2
SYSTEM ACQUISITION
In the current world, computing has been centered on mobile applications. This is
because of the convenience offered by this small computing gargets. Of all is there robustness
and flexibility forms the key thing to be considered in all mobile based applications, (Longoria,
2004). System designers should be keen on application designer to make the convenience to the
user because if the applications loose the track of mobile design they can easily mean another
thing to the user.
Every business an organization should target on using mobile applications. This forms
the basic reason every organization should think of going mobile. Organizations can deliver
useful information to their customers and through mobile phones
The acquisition strategy is best managed through controlling and executing financial
plans. Project realism is one of the main factors to consider. This has been catered since there are
enough seasoned application developers. Every functionality proves to be possible and can be
implemented.
Resource balancing has also been catered in the project. The major resources for this
project regard to skilled personnel. The company has enough seasoned programmers to handle
the application development in an agile way. This means that the application modules will be
developed by different groups and later on merged. This increases flexibility and saves time.
The company has enough financial resources. This can sustain the project during the
development of the application. The company has risk handling funds in case things go a bit
astray from what has been planned.
3
SYSTEM ACQUISITION
The system being featured is for a non-profit organization that helps control drought
effects in dry areas. Since the survey is important, there was a need to develop a mobile
application that can be used by respondents in answering a questionnaire based on the
organization’s research area. This helps reduce the physical work of filling and analyzing papers.
The application helps reduce data loss that can be incurred from paper work.
The company has seasoned team of workers who can bring the project into realization.
This includes a team of seasoned programmers in mobile application development. The
programmers have been involved in the earlier development, and they are well grounded with
what they are doing. The team’s project manager has got sound management techniques (Harrin,
2015). This means that the project will be managed in a way that will minimize expenses while
maximizing output.
This project can be completed within a time frame of one month. One week can be used
for system analysis. Two weeks can be dedicated for system development. Here the developers
can be involved in the real system development. In the last week, the application can be launched
for testing. If it passes, then it can be launched for use. Below is a decision matrix for weighing
choices for the project.
Experience
Timeliness
Budget
Total
Outsourcing
4
3
3
10
In-house
5
4.5
4.5
14
development
4
SYSTEM ACQUISITION
The word n-tier is used to refer to a ‘multiple number of tiers’. Therefore an n-tier
application is a type of application that is shared among three or more machines on a given
network. In this case, the user interface programming is found in the user’s computer while the
business one is found in the one that is in the center of a network. Finally, there is a computer
that manages a database where all the data needed in a network is stored. The n-tier system
mimics the client-server model. This is because in the client-server model, there are three and
above tiers that are used. (Magoutis,et al 2007, May).
In other words, n-tier data applications are referred to as data applications that are split
into several tiers. This makes them separate the processing task into several discrete tiers that are
evenly distributed between the server and the client machines. The n tier system is made using a
well-developed architecture that consists of three tiers namely: presentation tier, middle tier, and
data tier.
Presentation tier
This is where the users get to interact with a given application. To make this simpler, let’s
take an example of a user operating a PC, he/she clicks on an application and it starts running.
That is simply what happens at this particular tier. The applications run on an application logic
which is contained here. The components that are contained in this tier include: data combining
components e.g. BindingSource and Bindingnavigator, Object representations of data e.g.LINQSQL. This tier connects with the middle tier by means of special data access component that is
located in the middle tier. (Manuel,et al 2003).
Middle tier
This one acts as a communication channel for the two tiers; presentation tier and the data
tier. The components within this tier that ensure communications between the mentioned tiers
5
SYSTEM ACQUISITION
include: adapters e.g. table and data adapters, Object representations of data e.g. LINQ-SQL, and
finally the usual application services that are found in computers e.g. personalization and others.
The diagram below shows the architecture in the visual studio and how it can be used in the
middle tier of the whole system. (Manuel,et al 2003).
Diagram from msdn.microsoft.com
From what we can see in the diagram, the middle tier is attached to the data tier through
the data connection feature which is found in the data access component within the system.
Data tier
This is simply the tier that has it all. In IT, the server is defined as a computer that stores
all the data that is needed on any given network. In this case, the data tier acts as a server that
houses all the data for the applications. Here, visual studio’s features can also fit as shown in the
diagram below:
6
SYSTEM ACQUISITION
Diagram from msdn.microsoft.com
As I said earlier there is no way this tier can be accessed directly by the user on the
presentation tier. The data access feature located in the middle tier plays a pivotal role in the link
between the two tiers. (Manuel,et al 2003).
In the project of designing this architecture, there are four requirements that are vital as
the question demands. The paragraphs below address the four requirements for this project.
Operational requirements
The designer must specify the environment in which the system must work and how it
fairs over time. There are four key operational requirement areas. They include: technical
environment requirements; this needs the specification of the software and hardware on which
the system will run, System integration requirements; where there is need for the system to
operate with the systems in the network, Portability requirements; which deals with the evolution
of operating environments over time, and finally the Maintainability requirements; which deals
with the business changes that may be anticipated. (Manuel,et al 2003).
Performance requirements
This one focuses on issues e.g. time, reliability etc. During the definition of these
requirements, they must be eligible for testing so that comparison of the requirements is made
easier. The important areas are: speed requirements; e.g. the processing speeds of a system,
Capacity requirements; e.g. how many users the system can support at one time, and finally the
7
SYSTEM ACQUISITION
Availability and Reliability Requirements; e.g. if people can get access to the systems anytime
they want to use it. (Manuel,et al 2003).
Security requirements
This is the capability of the system security agents to protect the information system from
unwanted incidences such as disruption, and data loss e.g. hacking, or hardware /software failure.
The operations group is responsible for installing security software on the systems. This depends
on the security requirements of a given organization. The security requirements include: system
value estimates, access control requirements, encryption and authentication, and virus control
requirements. (Manuel,et al 2003).
Cultural and political requirements
This deals specifically with the area that the systems are to be used e.g. different
countries around the world. The key aspect in this is the understanding of the global cultural and
political requirements for these IT systems. These requirements include: multilingual
requirements, custom, making unstated norms explicit and legal requirements.
Finally, the three possible interface and navigation design concepts include:
User interface and navigation
This is categorized under tier 1. It relies on the user’s experience. The functions of this
layer are: providing the GUI, provides user’s interaction with the app, input of data, and get
feedback of their queries, and the data management functions. In the web applications, the
browser takes the job that is to be done by this tier.
Business logic
It is categorized under tier 2, and acts as the communication channel.
8
SYSTEM ACQUISITION
Data services: Takes part in data storage for all the information that is required by the users on
the network.
THE DATA FLOW DIAGRAM
Questionnaire
pose questions
process
Questionnaire
Answer questions
Pose next
question.
rsepondent
feed responses
feed questionnaires
questionnaire database
send field data
central
analyzer
analyze field
data
PHYSICAL DATA MODEL
correspondent
questionnaires
Age:(int)
location:(string)
period of stay:(int)
level of education:
(string)
Age:(int)
location:(string)
period of stay:(int)
level of education:
(string)
9
SYSTEM ACQUISITION
DIFFERENCE BETWEEN LOGICAL AND PHYSICAL AND DATAMODEL
The logical model is getting the requirements of a business and converting them into a model; it
is general based on the business and not the database. It is all about business processes and
entities. The diagrams involved should show the processes and the data that exists. They include
the
i.
Entity relationship diagram.
Its goal is to give the developing team with an instinct of various categories of data for the
business that is involved and, in general, give out the relationship they have developed with one
another.
ii.
Business process diagrams
It makes the development team to know how data is being circulated within an
organization since it shows the activities of different entities within the organization; it
can be used to display the interface design.
Physical modeling
This is the actual design of the database regarding the logical modeling. It is the actualization of
the logical diagram and is represented to show how the database is organized in a sensible
manner. One can also have the need to describe the constraints involved, which include primary
10
SYSTEM ACQUISITION
keys and that also must get defined by the views. The physical model that is stipulated mostly as
being database software specific.
Data Model
A data model illustrates the relationship between data. It is, therefore, important in this context to
identify the relationship involved. This includes:
i.
Conceptual modeling
This requires the highest level of relationship between entities.
ii.
Enterprise Data Modeling
This addresses the specific requirement of an individual business.
iii.
Logical modeling
This will act as the one to be used to build physical data model since it shows the entities
attributes and relationships of the enterprise.
The objects that the application include:
i.
The correspondents
ii.
The questionnaires.
11
SYSTEM ACQUISITION
Class Diagram
CORRESPONDENT
QUESTIONNAIRES
age:(int)
gender:(char)
level of education:(string)
0..1
1..*
Type of question:(char)
Filling time :(char)
filling questionnaire
posing questions
The inheritance structure of the objects.
Questionnaires
The questionnaires are of two types: either specific or general.
The public and the surveys will be categorized into answered or not answered.
RESPONDENTS
The respondents will be subdivided into both literate and illiterate
12
SYSTEM ACQUISITION
References:
Harrin, E. (2015). 15 Skills Project Managers Will Need in 2015. PM Blog. Retrieved 29
November 2015, from http://www.esi-intl.co.uk/blogs/pmoperspectives/index.php/15skills-project-managers-will-need-2015/
https://msdn.microsoft.com/en-us/library/ms524900(v=vs.90).aspx
Longoria, R. (2004). Designing software for the mobile context. New York: Springer.
Magoutis, K., Devarakonda, M., & Muniswamy-Reddy, K. (2007, May). Galapagos:
Automatically discovering application-data relationships in networked systems. In
Integrated Network Management, 2007. IM'07. 10th IFIP/IEEE International Symposium
on (pp. 701-704). IEEE.
Manuel, P. D., & AlGhamdi, J. (2003). A data-centric design for n-tier architecture. Information
Sciences, 150(3), 195-206.
Purchase answer to see full
attachment