Expert answer:Creating Use Cases
Solved by verified expert:Using the Microsoft Word document created in W4 Assignment 2, add to it by including the following:A context diagramA set of level-0 data flow diagramsA set of level-1 data flow diagramsDiagrams that adhere to UML specificationsAn ER model that is consistent with the material you will turn in this week (The data stores and data flows in the DFDs should be consistent with the data model. The ER diagram should not show entities that are not present in the DFDs and should show all data stores [that accommodate all the data flows] shown in the DFDs.)An ER diagram that adheres to UML specificationsSupport your responses with appropriate research and examples.Cite any sources in APA format.
su_its3110_w4_a2_still_j.docx
su_its3110_w3_a2_still_j.docx
su_its3110_w2_a2_still_j.docx
su_its3110_w1_a3_still_j.docx
Unformatted Attachment Preview
Running Head : Creating Use Cases
1
Creating Use Cases
Joshua Still
South University Online
Creating Use Cases
2
Based on the survey and research, communication uncovers that organizations that send
the mobile application in which it appears to gain in organization observation and consumer
loyalty. Based on the research of respondents (72%) in the overview said that they have a more
positive perspective of an organization that has a mobile application. Furthermore, 81% said that
they will impart the positive experience to others (Nashe, 2017). Whenever asked, how an
application would expand their level of fulfillment, 35% were of the supposition that simple
change to a live operator from an application would well on the way to drive its use, while 21%
expect more functionalities in the application to better address their issues.
Use Case Sets of Applied Systems Analysis
In this case, there are five user ID, names with various specific main actor, complexity
and priority. To proceed this certain use Cases, here are the User Case IDs: User Case ID of B_2
with use Case Name of specializing the products. Its main actor is a buyer. The use case 1 would
be accountable to buy the items of Mobile application to a certain company. First, to have the
purchase items, this use case will coordinate to their company coordinator about the quality of
the product to buy. When the product or item is defected (Internal), there is always reserve
another item. The coordinator is the use case ID of C_2. The use case ID of C_2 as the product
coordinator will examine the product and to make it happen, then use case ID C_2 will have to
talk to the use case ID of D_2 which is the stakeholder. If the basis of methods applied by the
customer to the production of the products, or if they have any queries about some external
failure, the coordinator will have to proceed with them quickly and answer their queries as fast as
they can. There is an automated system that would handle the queries if ever the coordinator is
out of presence or unapproachable due to some instances.
Creating Use Cases
3
The stakeholder will handle the mobile application to the customers for them to connect
within. The stakeholder which is the use case ID of D_2 will now begin to have a collaboration
with the technical team for some assistance in the implementation of the mobile application for
the company of Black Diamond Sports. The Stakeholder has a critical function or role to have a
comprehensive project and planning. When the failure of the mobile application (Temporal) in
connecting to the customer trigger due to any reasons, the stakeholder will do some check
quickly with the help of the technical team. Next is the use case ID of E_2, its main actor is to
arrange the payment. The mode of payment used to deliver or to have the product is PayPal. In
this case, the use case ID of E_2 will have to handle all the methods or procedure on how to
make a transaction online with the customers in the Black Diamond Sports company. The
Trigger of this step is that, when there is encountered failure in the system (Internal) that is said,
there is no detailed receipt given right after the purchase process.
When it happens, the use case ID of D_2will quickly calls the technical team who are
actively delivered their 24 hours supports in all cases or issues encountered both the customers
and the system or application. The successful online purchase or any transaction would be
delivered by the use case ID of F_2. This use case ID will handle all those items that have been
purchased in the online shop using Papal payment. When there is a trigger regarding the shipping
(External), the use case ID of F_ 2 will accommodate it quickly through monitoring
automatically with the use of other tools recommended by the technical team. The deliberation of
the item purchase online would be within 12 to 24 hours right after the time of purchase. The use
case ID of B_2 would start its main actor within the duration time and schedule 18 hours a week
together with the use case C_2 and D_2. The use case ID of E_2would begin 21 hours a week
and the use case ID F_2 will also begin within 25 hours a week.
Creating Use Cases
4
Below is the UML Format of the Use cases:
It is important that the customer should have a proper communication or interaction with
the company the wanted to purchase any kind of items for and vice versa for the company’s part.
Just let us take an example, if the customer wants to extend their comments or any queries to the
certain company, they must use a high-quality technology for proper communication and, when
it comes to buying or purchasing products, Anamika says that “online shopping is faster and
efficient rather than going outside and there you will experience hassle and bad experiences”
(2017). The implementation of the mobile application of Black Diamond Sports company for the
benefits of customer’s satisfaction is very useful for them to derive proper services with hasslefree and convenient way.
Creating Use Cases
5
References
Anamika, S. (2017). Top 10 Benefits of Online Shopping That Make Your Life Easy. Retrieved
from https://toughnickel.com/frugal-living/Online-shopping-sites-benefits
Dennis, A., Wixom, B. H., Roth, R. M. (2015). Systems Analysis and Design, 6th Edition. [South
University]. Retrieved
from https://digitalbookshelf.southuniversity.edu/#/books/9781119088493/
Nashe, L. (2017). The Significance of Mobile Application on Business. The journal of the
Technological system. New York: Brian & Cammey.
Running Head: SU_ITS3110_W3_A2_Still_Joshua
Joshua Still
South University Online
Elicitation Techniques
1
SU_ITS3110_W3_A2_Still_Joshua
2
Elicitation techniques.
An elicitation technique is any of a number of data collection techniques used in an
array of different fields such as management, education, counseling, philosophy, psychology,
engineering, and cognitive science. Elicitation, where knowledge is devised or sought directly
from human beings, is differentiated from indirect methods such as gathering information
from written sources. Individuals interacting with people with the aim of eliciting information
from them may be called an analyst, experimenter, knowledge engineer or an elicitor
depending on the field of study (Cooke, 2004).
The elicitation techniques include interviews, observation, surveys, brainstorming,
focus groups or behavior in laboratory setting or analysis of assigned tasks. Requirements are
discovered by analyzing data. Requirements of techniques must be elicited, or drawn out and
the methodology of eliciting these methods must be meticulous and logical.
The errors or mistakes made in elicitation have many times resulted to significant
causes of complete system failure or abandonment of the project, and this has a substantial
cost in the expense of fixing the mistakes. The purpose of requirements of elicitation,
therefore, is to thoroughly identify the business/project needs, risks and the associated
assumptions with such projects.
The first step in the requirements of elicitation technique is for the analyst to glean an
accurate and comprehensive understanding of the project’s need. With this top understanding,
it makes it easy for the analyst to select the proper stakeholders and elicitation techniques.
The second step in the requirement for elicitation techniques is for the analyst to ensure that
an adequate mix and amount of stakeholders are secured and are actively engaged in defining
SU_ITS3110_W3_A2_Still_Joshua
3
the requirements for the entire project duration. These stakeholders may include suppliers,
customers, project financiers, the project manager, implementation team, and the operational
support team and many others according to the unique needs of the project.
After the analyst has recruited the appropriate stakeholders based on the unique
project’s needs and chosen the methods by which he will elicit requirements, he is bound by
responsibility to schedule the time for carrying those techniques with the stakeholders in
advance to ensure that they participate their parts within the required duration. The analyst
now determines the best techniques for eliciting requirements phase that should be applied
appropriately.
The requirement elicitation that should be used is taking what one sees. The
brainstorming technique should produce numerous ideas, set ground rules, the criteria for
evaluating and rating these ideas and set a time limit. This improves productivity and
motivation of all stakeholders in the project.
The document analysis elicitation is vital when drawing out information from existing
documentation. This is very helpful especially when the subject matter experts are not
available or have already parted ways with the project organization. The analyst then uses the
relevant documentation to study and understand the required details. This information is
stored in documents such as project plans, project charters, and contracts, statements of work,
memos, emails, project rules, and training materials.
The requirements for elicitation techniques also are important in drawing information
from a select group using a moderator. This is the technique referred as focus groups. This is
usually depicted as a very formal and more structured process promoting discussion by the
SU_ITS3110_W3_A2_Still_Joshua
4
skilled moderator to the 6-12 attendees engaging them in a neutral conversation saving time
and cost from not conducting many individual interviews.
The requirements for the interview elicitation technique I also believe should be used
on individuals to uncover information should depend on the knowledge of the interviewer and
the interviewee to reach a consensus on the documented either formal or informal questions in
devising the relevant required information (Davis, 2016).
The requirements for the observation elicitation technique depends on the sharp and
active mind of the observer to take notes or document almost all possible scenarios the vital
information that is relevant. Though it may be time consuming it is a model that generally
puts the observer out of the way of those being observed and now cases of pretense to the
normal realities are minimized because they may not be aware and this gives credible
information. A good example is when conducting a project on a population that holds their
cultural values in high regard.
Surveys or questionnaires efficiently elicit information from many people within the
stipulated time frame to an appropriate audience with a specific purpose when answering the
clear and concise questions whose range of possible responses are very well understood and
easy to analyze.
The documentation as required by the requirements elicitation plan would be to create
a system that fits most of the essential features and leave the lesser parts for a later update.
After the processes I identified earlier of identifying stakeholders then requirements for
elicitation where the information gathered from multiple stakeholders is defined and the
analyst draws out from each group on what the applications are meant to accomplish the focus
SU_ITS3110_W3_A2_Still_Joshua
5
turns to structured interviews where well-articulated questions are devised for the customers
to give their information on what they think about the project and if it is helpful to them in
any way.
This now shows why the techniques can be combined to achieve the results that one
want out of his or her project.it is difficult to do a stand-alone activity when digging into any
technique. For example, if it is in interviews, one will require some documents analysis first
to come up with a list of questions or to get the interviewers to give the best information, they
first need to see the prototype.
The nonfunctional requirements are the less effective ones in a project which an
analyst should not spend a lot of time on because at the end they will lead to creep and
wasting of time building the wrong thing. When analysts invest a lot of time on background
research that is not specific to the project in reading books, articles, and websites, they end up
providing a basis for understanding the business or project situation but not identifying the
particular project’s requirements. When analyst also spends a lot of time reviewing the project
related documents it may help in solving errors but cause delays in full project
implementation and completion. An example is when effective requirements discoverers use
various techniques to examine and follow up on findings of a project and at last end up
investing a lot of energy becoming better at requirement discovery techniques rather than
addressing the relevant project need.
SU_ITS3110_W3_A2_Still_Joshua
6
References
Cooke, N. J. (2004). Varieties of knowledge elicitation techniques. International Journal of
Human-Computer Studies, 41(6), 801-849.
Davis, A., Dieste, O., Hickey, A., Juristo, N., & Moreno, A. M. (2016, September).
Effectiveness of requirements elicitation techniques: Empirical results derived from a
systematic review. In Requirements Engineering, 14th IEEE International Conference
(pp. 179-188). IEEE.
Dennis, A., Wixom, B. H., Roth, R. M. (2015). Systems Analysis and Design, 6th Edition. [South
University]. Retrieved
from https://digitalbookshelf.southuniversity.edu/#/books/9781119088493/
Running head: W2A2 – Joshua Still
1
Applied Systems Analysis
Joshua Still
South University Online
W2A2 – Joshua Still
2
Introduction
Also referred to as application development life cycle, system development life cycle is a term
that is used in information systems, system engineering and software engineering to describing a
process of creating, planning, testing and deployment of information. SDLC applies to range of
software and hardware configurations, as a system can only be composed of software, hardware
only.
In our project, we will involve in process of creating, planning and installing software and
system. We are aiming to come up with a software and system of high quality that meet the
customer expectations basing on their requirements, through delivering systems, which move
through a clearly a clearly defined phase. We will make sure that the project meets the cost
estimate and time frame (Cleland, 2016).
Steps in the Project schedule
Step one: definition of the schedule activities
We will establish a Work Breakdown Structure and establish work packages. We will
decompose them into schedule activities. We will also decide what kinds of activities are needed
to create the work packages. For instance, if one of the work packages is to configuring computer
hardware, our scheduling activities will include setting up network configuration, application
installation, installation of video card and setting up mail client (Cleland, 2016).
Step two: sequencing the activities
W2A2 – Joshua Still
3
The schedule activities will be sequenced by placing them in order. For instance, in one of our
work schedule, we will have to set up network configuration, install the video card, set up mail
client and install application.
Step three: estimating the needed resources
We will involve in estimating the needed resources to successfully accomplish every given
activity. This will include estimation of required financial resources, team resources, and
equipment.
Step four: estimation of the duration of each activity
We will analyze how long it will take to successfully accomplish each activity. The estimates
will be quantified through the following tools:
Analogous estimation- we will take a top-down estimation approach for successful completion of
the project
Expert judgment – professional and experienced software engineers will be hired to enhance
smooth running of the project
Step five – schedule development
Tools such as schedule compression, critical path method, what-if scenario analysis, critical
chain methods, and resource leveling will be used to optimize the project schedule.
Step six: controlling and monitoring the schedule
Appropriate measures will be taken to ensure effective controlling and monitoring the schedule.
Scheduling change control systems, progress reporting, variance analysis, and performance
W2A2 – Joshua Still
4
management will be used to determining if additional actions will be required for project
completion.
Plan for the project’s progress assessment
To ensure successful progress of the project, following measures will be considered:
Clear definition of the project scope – every means will be taken to ensure that the project scope
is well-defined and its objectives, methodology and budget are clearly established. This will be
usually done through arrangement of meeting or forum with the organization’s management and
other concerned staff.
Careful selection of the team members – once the project scope has been defined, talented and
skilled software engineers and other professionals will be carefully chosen to carry out the
project. A careful selection of these individuals will help to ensure the project is completed
without drawbacks.
Clear outlining of the goals
In order to have a clear of what to expect for final product, goals will be outlined that
measurable, specific, realistic, attainable and timely.
Creation of staffing plan
A staffing plan will be established to detailing the project’s human resources requirements how
they will be achieved. The staffing plan will be comprised of several sections:
Project staffing estimate – this involves identifying the estimated staffing requirements
Project responsibilities and roles – responsibilities for each staffing roe will be summarized
W2A2 – Joshua Still
5
Acquisition strategy – we will describe how, when and from what staffing sources will be
acquired
Training plan – we will involve in identifying the skill gaps and details that are specific staffing
training for the team members (Cleland, 2016).
Establishment of the organizational chart – the project report relationship will be accurately
displayed.
Communication plan
Different items will be included in our communication plan such as Review, Project Kick Off,
Team Meetings and Status. Ample time will be spent in gathering inputs from relevant
stakeholders to ensuring the plan is comprehensive. We will also create a dialogue among the
organization’s key stakeholders and employees to ensure they understand our project. We will
educate them about the important of the project and why it should be implemented. Further,
feedbacks for opportunities will be provided to ensure that the project is well understood
(Cleland, 2016).
Various methods will be used to communicate our project to relevant stakeholders including:
•
Status report
•
Meeting summaries
•
Surveys
•
Newsletters
•
Formal presentations
•
Intranet/internet web page
W2A2 – Joshua Still
6
•
Lunch workshops
In addition, we will include matrix in our communication plan for clear definition of various
roles. In this matrix, we will define topic of discussion, key objectives, delivery method,
audience, frequency and roles. This will help in setting our expectations and boundaries for the
project communication plan.
Risk-management plan:
There are many uncertainties in the projects that are carried out in different areas. These
uncertainties are majorly referred to as risks that may be incurred in the process of conducting a
given project. It is, therefore, vital for these diverse types of risks to be identified earlier before
they take place and can interpret what might go wrong. This added with analysis on how they
can be well controlled is known as risk management (Barkley, 2004). Risk management is very
important in assisting projects to be successful after a long run. Risk management is necessary
for many projects to achieve their goals and this paper mainly discusses on how some already
identified risks can …
Purchase answer to see full
attachment
How it works
- Paste your instructions in the instructions box. You can also attach an instructions file
- Select the writer category, deadline, education level and review the instructions
- Make a payment for the order to be assignment to a writer
- Download the paper after the writer uploads it
Will the writer plagiarize my essay?
You will get a plagiarism-free paper and you can get an originality report upon request.
Is this service safe?
All the personal information is confidential and we have 100% safe payment methods. We also guarantee good grades