Task 01 To Task 03 SAD
Task 01 To Task 03 SAD
Traditional Methodology
The traditional methodology was the first process methodology introduced. The traditional
methodology or the waterfall methodology is a linear project management approach which
gathers the needs of stakeholders and customers at the beginning of the project and creates a
sequential project plan to achieve their business objectives and aims. It is also known as the
sequential life cycle methodology. The traditional methodology is named as waterfall
methodology because each stage of the project draws on the next. It is a detailed, structured
methodology that has been around for a long time as it works. Some of the industries that
regularly use the waterfall model such as construction, IT and software development. Traditional
methodology is very simple to understand and to use in practical scenarios. In a waterfall model,
each stage must be completed before the next stage can begin and there is no overlap of stages.
In traditional methodology, there are main five stages. [ CITATION Wat15 \l 1033 ]
1. Requirement
a. Project Scope
b. Stakeholder Expectations
c. Research
d. Assemble team
e. Kick-off
2. Design
a. Collect Tasks
b. Create Schedules
3. Implementation
a. Assign team tasks
b. Monitor & track
c. Manage resources & workload
d. Report to stakeholders
e. Test
f. Deliver app
4. Verification
a. Pay contracts
b. Create Templets
c. Close output
d. Celebrate
5. Maintenance
Agile Methodology
Agile methodologies are approaches to product development that are consistent with the values
and principles described in the Agile Policy Statement for Software Development. Accelerated
methods enable small and cross functional self-organizing groups to distribute small portions of
activity more and more frequently, with consistent customer feedback and, as needed, course
corrections. Also, aim of the agile methodology is to address the challenges faced by traditional
methodology approaches to delivering great productivity in the long run, during which time
customer needs change and its products are misrepresented. Another thing is, Agile is a repetitive
methodology, which means that developers can work on a project platform and make as many
changes as they need to revisit and conclude when it is finished. This flexible feature of the agile
methodology is different from the waterfall method and cannot be reviewed once it is finished.
Using Agile methodology permits you to move faster with development through a simple
working method with long and short linked documents. It also uses the time-box concept, which
means that the conclusion is based on chronological features rather than features, and the
purpose of this methodology is to set a time frame and try to make as much development as
possible within the time frame.[ CITATION dig18 \l 1033 ]
Faculty of Engineering & Assignment: System Analysis & R.M.L. Madushan Jayathilaka
Technology National Diploma in Design M19931227005
Computing
Figure 1
Figure 2
production, all activities are performed in active groups. Each department of the organization is
equipped with a leading technical specialty. All projects flow through operational departments so
take advantage of modern technology. So, the system is well suited for mass production. When
we consider the communication, the communication channel is vertical and structured for the
formal and informal organizations. The authority level and responsibility of organizations is well
defined as each person reports to only one person. When we consider the efficiency of the
traditional methodology, it has long proven to be effective in delivering the desired products to
customer satisfaction. When a strategic management system leads to success, it builds trust
between the organizer and the client, and that strategy is considered for future projects. It has a
positive effect on the employee, making them more experienced and specialized to carry out
complex activities and perform more challenging projects. When we consider the structure, it has
clear and well defined steps to follow. Also, it determine the final goal very clearly. A definite
step in the traditional methodology, is the commitment to a final product, goal or distribution at
the beginning, and teams must avoid deviating from that commitment. For small projects where
the objectives are clear, this step will make your team aware of the overall goal from the
beginning, making it less likely that details will be lost as the project progresses.[ CITATION
Ana12 \l 1033 ]
Figure 3
have invested a considerable amount of money in a project under very specific, meticulous
assumptions. A sudden change in the parameters of the project will nullify most of the work you
have done so far, thereby discarding the entire timeline. If your team's projects are unpredictable
or involve constant changes, consider adapting the waterfall to allow more reflection and
revision, not just on the go, to avoid wasting time and energy. As an internal process, traditional
methodology consider very little attention to the user or client involved in a project. Its’ main
objective is to help internal teams move more efficiently through the stages of a project that can
work well for the software world. However, if you work in an industry other than software,
clients often want to be involved during a project, to gather ideas, and to explain what they want
as the project progresses. If you have clear, unchanging goals from the beginning of your project
and you are not responsible for updating end users or clients through the development process.
At other times, consider a quicker approach to better anticipating change and educating
stakeholders through the life of the project. By contacting the stakeholders, you reduce the risk
of late requests for changes by discarding your project deadlines. Saving the testing phase until
the end of a project is very risky, but traditional methodology insists that teams wait until the
fourth or sixth step to test their products. Outside of the software industry, the testing phase
means which showing a client a new web design, advanced testing content, or taking a number of
steps to gain empirical data on project feasibility. [ CITATION Luc16 \l 1033 ]
When we consider about the customer interaction of the agile methodology, the user or customer
haven’t enough time to spend with the developers, or if the main customer is a top level
manager. The development team and end users are in the same physical location on a daily long
term basis, which is not applicable in all situations. Another thing is the difficulty of
coordinating between groups for large projects. This methodology do not have long term plans to
talk about the fast paced methods. It means that when the various components of the project are
assembled this will definitely cause some problems. This procedure called as “refactoring”. This
can lead to poor documentation due to the rapid algorithms based on verbal communication with
customers. Working in large groups can make it difficult to identify individuals' contributions
and how they can be happy. In addition, the lack of adequate documentation to track overall
progress faces major challenges that are not entrusted to the executive managers. Another thing
is, only the senior program programmers have the ability to make the necessary decisions in the
development process. So it has no place for new programmers if it is not integrated with
experienced resources. [ CITATION Ade14 \l 1033 ]
Figure 5
Strengths
When we consider about the complexity of the traditional and agile methodologies, I think
traditional methodology is more suitable for small or less complex projects as it follows a linear
approach. Sudden changes or other complications in the project can block the whole process and
force the team to go back to the first step and restart. But agile methodology is the best
methodology to follow in the complex projects. A complex project can have different
interconnected stages and each interconnected stage depends on more than one stage as in simple
projects. Therefore, agile methodology is suitable for large and complex projects. Also we
consider about the adaptability of the traditional and agile methodologies, I think traditional
methodology works in the belief that it will not be reviewed once a phase is over. So, it does not
adapt to rapid changes in the work plan. The traditional methodology fails to adapt to new
changes if any unexpected need arises or any change is required. The only choice is to start all
over again or restart the project. This is a huge effort and a waste of time in the process. But agile
methodology the adaption is very high as it is not linear. Complex projects consist of several
interconnected phases, where one phase of change affects another. Project managers and project
owners can take calculated risks in such cases as there is a high chance of adaptation. When we
consider about the scope for feedbacks and changes of the traditional and agile methodologies, I
think each process of the traditional methodology is clearly defined and defined at the beginning
of the project. It cannot deal with a major change or feedback that may require a change in
process. The project submission times and budgets are fixed and rarely allowed to change. But in
agile it has a high acceptance for feedback and modification. The process of the agile
methodology is very flexible and it gives the permission for constant feedback which helps to
provide better feedbacks during the fixed project delivery period.[ CITATION Kir19 \l 1033 ]
Weaknesses
First we look at the agile methodology. Agile is simple to understand in principle but difficult to
do well in practice in practical. It requires real commitment and the first attempts will not be so
successful. It is impossible to predict what will be given in the end. Agile methodology requires
a high level of collaboration and constant communication between developers and users. This is
always appropriate but may not always be possible and requires continued commitment and time
from the business and developers. Also, agile methodology is very intense for software
developers and users. If the software developers are working on multiple projects at once, there
may be reasons to avoid this. Speeding up can be challenging when there is a supplier and
customer relationship. Customers generally want to know what they are getting for their money
as soon as possible. Agile methodology normally only address product development, while large
scale projects can be made up of many other components. When we consider about the waterfall
methodology, communication can be more risky especially when there is a perinatal review of
outputs or distributions, or when one side communication is used to articulate needs. Also, the
risk in the waterfall methodology can be quite high. If you add this to the high cost of making
changes to a waterfall project later on, it is easy to see why some of them are so expensive, too
late and too late. [ CITATION Kev16 \l 1033 ]
Creating new ideas and train the staff members is a recipe for disaster. Many professionals are
accustomed to one type of work and switching to quick habits without any kind of guidance can
lead to failure. The consultation stated that it is essential to hire a specialist in the agile
methodology of your choice to properly train the staff. These sessions help the team members to
understand their role in the system and ensure that their expectations are met quickly.
Organizations can quickly find books, blogs, and conferences to help organizations gain an
understanding of the topic. There are a number of options that can help decision makers provide
the best possible training to enhance their team skills and support agility. Assume that the goal is
to get into agile methodology, we should try to take an approach that focuses on retrospective
and short feedback cycles to meet specific challenges in our organization. We do not have to be
fast because all of our competitors do it. Forced activation of leadership without activating self-
help groups. We want to help our organization lead to quicker approaches, but their role should
be to point the direction. People who are close to the task should be the ones who figure out how
to do it. Individuals who are involved in middle level management have the means to provide air
coverage and to find ways for teams to gain the skills and support they need. Quick approaches
are needed but not enough. If you really want to be the most effective organization you need to
look at your decision making and portfolio management. Even if you are diligent, you will not be
able to do all the work you want. You still have to make tough decisions about what not to do.
Pay more attention to uses and tools and do not know why you are so diligent in the first place.
To do this, Agile requires a great deal of training. The transition to a agile methodology affects
to the whole organizational structure. Resistance can be found in all of these elements, because
the structure changes and people are normal used to spend a lot of time creating non-coded
artefacts, Attend meetings and follow rigorous work processes. Therefore, they usually tend to be
based on plans and processes. [ CITATION Fer17 \l 1033 ]
Task 02
Functional Requirements
1. Authentication
a. Login
b. Logout
2. Authorization
a. Use Role Check
3. Process Data
a. Display
b.
c. Edit
d. Search
4. Leave Application
a. Leave application
b. Leave approval
5. Report Generation
Figure 7
Task 2.2 Feasibility Study
Feasibility study is a procedure which is conduct to recognize objectively and logically the
strengths and weaknesses of an existing business or proposed business, the opportunities and
threats around the business environment, the resources needed to move forward, and ultimately
the prospects for success. In its simple way, the two criteria for doing feasibility are the cost
required and the value to be achieved. A well designed feasibility study should provide a
business or project background, historical background, description of a product or service,
accounting statements, operations and management details, marketing research and policies,
financial data, legal requirements and tax liabilities. Basically, feasibility studies are doing prior
to technological development and project implementation. Feasibility study evaluate the
potential for project success. Therefore, it is an important factor for the reliability of the study for
potential investors and lending institutions. So, it must be conducted in an objective, unbiased
manner to provide information on which decisions can be based.
Feasibility study helps to provide legal and technical proofs of project importance, sustainability
and cost-effectiveness productivity. The reporting process allows to the senior management to
obtain the information needed to make valuable decisions about budgeting and investment
planning. Also feasibility study helps to develop solutions for project analysis. Also, it helps to
link project efficiency to budgeted costs. Another thing is it helps to reduce the risk because it
helps in the development of emergency planning and risk management strategy.
In each and every feasibility study there is a structure. When we write to starting the feasibility
study firstly we must create a title page that provides a detailed but brief title, including the
author's name, email, workplace, and the organization in which you are writing the report. At the
body of the feasibility report, each page of the report should consists with a descriptive title with
a short title for the report, the author's name and page number. Also it can be include headings
and subtitles and display this structure in the document content. Furthermore there are some
important sections to include in the feasibility study. They are executive summary, background,
analysis, alternatives and options, cost benefit evaluation, conclusions and recommendations.
[ CITATION May17 \l 1033 ]
The importance of a feasibility study has been debated in many companies for over the years.
Out of the debate are those who think they know what the public wants and who are actually
testing to make sure their assumptions are true. A proper feasibility study can clearly recognize
the target audience with their purchasing power. This procedure determines the economic
viability of a business proposal. This thing is an important part of a business case and should be
done after creating a business idea but long before it is technically developed and before any
product is launched. In summary, a feasibility study is the determination of the viability of a
business in a specific area or business sector. This is the process of identifying the potential
problems between product acceptance with the customer and how profitable the business can be.
It does not make a business as a good business opportunity because it has a large and necessary
product for a region. Not all ideas that make sense are great business opportunities. For example
selling water bottles in a desert, it is a good idea because there is a lack of water. But since water
is scarce, there is no living population and sales will not exceed the cost of importing water to
the arid zone, which is not a good and viable business. What can be learned from a feasibility
study can better help a business and a project manager to determine if a business is profitable. In
the study, the transport activities of the business must be determined. If there is a problem, can it
be overcome in a profitable way. A feasibility study can reveal the right marketing strategies.
Also, it determines how to properly reach target audiences is an important step in creating a
viable business in any region. The location of the business and how it can be accessed by the
target audience will also be a factor. An effective feasibility study can determine whether your
product or service is needed, whether the customer has the ability and willingness to spend for it,
and whether they have access to it when they need it. If a business misses this step in their
product growth, they are better off throwing away their investment in dollars.[ CITATION
DrA16 \l 1033 ]
A large part of resource determination has to do with technical feasibility assessment. It consider
the technical requirements of the proposed project of the DT. The technical requirements are
compared to the technical capabilities of the organization. If the internal technical capability is
sufficient to meet the project requirements, the system project is considered to be technically
feasible. The analyst should find out whether it is possible to upgrade or add current technical
resources to meet the demand under consideration. This is where the specialization of system
analysts comes in handy, as they will be able to answer the question of technical feasibility using
their experience and their relationship with vendors. Project size is also included to the technical
feasibility. It can be determined by the number of project team members, project duration,
number of departments involved, or effort put into programming.
Measuring the economic feasibility impact has become a powerful and persuasive tool for those
seeking to grasp and testify to the potential financial benefits of hosting a major event.
Measuring economic impact not only permits public sector entities to assess the economic
returns on their investments, but also shows how events provide economic benefits allowing
event organizers to develop practices that maximize these benefits. The economic impact of a
major event refers to the amount of additional costs generated within an area defined as a
consequence of the staging of the event. For many events, spending by local area visitors is the
biggest factor generating economic impact. However, spending by event organizers is another
important factor. Economic impact studies generally seek to verify the net difference in a host
economy .In other words, to measure cash inflows and outflows to confirm net returns.
To assess the financial feasibility, management should analyze the costs and benefits associated
with the proposed project. The capital cost of a project affects the economic value. Cost
estimation is essentially an intelligent process that seeks to predict the final outcome of a future
capital expenditure. Although it may not appear that a definite number of costs and benefits can
be presented for any project in the early stages of the development process, sufficient time
should be taken to assess the cost and benefits of the project compared to other alternatives.
[ CITATION Pav08 \l 1033 ]
Task 03
Task 3.1 Fact Finding Techniques
Fact finding is the procedure which is used to gather data and information based on technical
methods, such as sampling existing documents, research, observations, quizzes, interviews,
prototyping, and integrated needs planning. Systems Analyst uses search engine optimization
methods to implement and improve an existing system. It is very important to gather the facts
needed to apply the tools in the system development lifecycle because that tools cannot be used
efficiently and effectively without properly quoting the facts. Finding methods are used at an
early stage of the system development lifecycle, including the system analysis phase, design and
post implementation review.
Interviews
An interview is the most common qualitative research method that uses in primary research. We
can get real-time data by interviewing people because we can ask questions face to face. Also,
we can match the responses by identifying the body language of res-ponders. It helps us to build
trust between researchers and res-ponders. The questions must be neutral, sensitive, and
understandable for the participators. We must ask effective questions to gather meaningful data
for the research. The researcher must have conversing skills, questioning skills, and listening
skills to conduct successful research. We must choose a suitable place to conduct an interview.
The interview time is depending on the research topic. It can be taking up to 2 to 6 hours.
Focus Groups
In a focus group, it includes 5 to 10 respondents with a mix of ages, genders, experiences,
professional statuses, and educational statuses. It depends on our research topic. The data
accuracy will increase with more respondents. If we ask difficult questions to the members, their
answers will not be in the correct way. We cannot get the expected answers for our research
topics.
Survey
A survey can be conducted with a target group or multiple groups. We can get very accurate
information by comparing the results of target groups. The questions must have a clear language
to understand. Also, it should have correct grammar and spelling. There are different types of
questions that can include in the survey. Such as multiple-choice questions, close-ended
questions, rating scale questions. We can conduct a survey by face to face and with phone calls.
These days, online mediums are used to gather information for the surveys. Email is the first one
of that. It is the most effective method to collect data for a survey. The response rate is very high
in emails. There are some features to send out and collect responses such as the "Questionpro
email management system". Also, SMS is the time effective and easy method to collect data. We
can print a URL link of the survey as a QR code on a book or article. This is the latest method to
get access to the survey.
Observation
Data and information can collected by observations. This method requires more time because
researchers need to collect data on their own. Observation are mainly have two types. They are
structured observation and unstructured observation. In structural observation, data is collected
by using specific variables. In unstructured observation, there are no predetermined variables.
Researching
Researching is more useful to finding facts about the application or the problem you are dealing
with and want to put it into a report or as an answer for an academic question. Computer
business magazines, reference books, and the Internet are good sources of information on how
others can solve similar problems and whether there is any software package to solve or partially
solve your current problem. [ CITATION Pad15 \l 1033 ]
For my system analysis I choose survey method to gather data and information to my project.
In fact finding techniques, I have chosen the survey research method to gather information for
the project because this method is the most appropriate method for nowadays. Also, we can
analyze our data with simple analytical technics. A survey is a simple method to collect
information about a service or a product from a sample of people.
According to the above survey methods I choose Google Form. It is a web-based survey. In the
survey method, the web-based survey is the most effective method to collect information. Email
surveys, SMS surveys, Google Forms are the few examples for it. By the way, Google form is
the main method of the online surveys. The analyzed data is present by the charts or tables.
When we look at these charts and tables, we can get a better understanding of our research topic.
Also, we can apply these research methods to many people. For example, when we create a
Google form to gather information, we can easily send it to many people by a single click. We do
not need to analyze the responses because responses are automatically analyzing by the
analyzing option on the google form. Also google forms are relatively inexpensive. Online
surveys and mobile surveys, in particular, cost very little per respondent. Another thing is
respondents are given incentives, the cost of a response is often much less than the cost of
conducting a paper survey or telephone survey, and the number of potential responses can be in
the thousands. Furthermore, google surveys are useful to describe the characteristics of a large
population. No other research method can provide this comprehensive capability, which ensures
a more accurate sample to reach conclusive conclusions and targeted results to make important
decisions. The anonymity of google surveys give the access to the respondents to respond with
more honest and valid answers. In order to get the most accurate data, respondents should be as
open and honest as possible with their answers. Google surveys conducted anonymously provide
a way for more honest and skeptical responses than other types of research methods, especially if
it is clearly stated that the survey answers will remain completely confidential. [ CITATION
Sus17 \l 1033 ]
Task 3.2 Fact Finding Analysis
Figure 8
Figure 9
I send my google form to 50 employees who are work in the several departments in DT
Technology to gather their ideas and information about the existing file basis employee
management system and existing payroll system. Basically I chose 25 low level employees and
25 higher level employees. So, their age, knowledge, experience, work experience in DT, ideas,
behaviors, thinking patterns are differ from each other. By that, I can get accurate and effective
ideas to my proposed system.
Figure 10
When I consider the current status of the existing employee management file based system, most
of people said they are satisfied about the current system in 50% percentage. From that I can get
a conclusion about the system. Some tasks or the activities of the current system is okay to some
employees and some tasks or the activities they not satisfied. So, we have to identify the
weakness points of the system and try to solve that in the proposed system. Nine of employees
are not satisfied about the current system. These nine people are very important to us because
they know the whole system and they also know the tasks or activities which needed to be
developed. Twelve of people are totally satisfied about the current system. We can identify the
strengths of our current system from them. So, we can improve the system by their valuable
ideas. But fourteen of people said they have no idea about the current system and its’ whole
process.
Figure 11
In the current employee management file based system, I have main five categories. When we
consider the leave management, every employee have to fill a leave application to get the
approval for their leave. They can mentioned the leave type (Half day, Full day, Short leave),
leave category (Annual, Casual, Medical, Special), name, employee number, leave period.. Then
they have to submit that document to their report person. In some situations, employees cannot
get the approval form their report person due to some reasons. Some times their report persons
are in important meetings, sometimes they were on leave likewise the employees cannot get the
approval immediately. That’s why I think eight employees said the leave management is need to
be developed. When we consider the absence management, most of employees said the absence
management procedure is need to develop immediately. Presently, employees have 21 days
annual leave, 7 days casual leave and 14 days medical leave for an employment year. But some
of employees cannot calculate their remaining leave days due to their personal reasons. Also,
supervisors cannot track their team members’ leave history. It is a critical problem. So, that thing
is very important to develop at the proposed system. Attendance ad overtime management is
very important fact because it directly impact to the employees’ salary. Store management is
how to store the employee data. Currently, they are stored in files which have unique number to
identify the employee. So, that files can be destroyed due to some reasons. Therefore the
employee details should be store in a cloud database or a system. Another thing is we cannot get
the details when we need it because we have to search one by one file or file raw. These kind of
issues and errors are in the existing system.
Figure 13
The accuracy is very important to every system. Most of employees said the accuracy of the
current system is okay to them. But the thing is, similar to that 23 employees said they cannot
depend on the data of the current system. They think the information of the current system is not
okay for them. So, we have to consider about the reasons for that. Therefore we to pay attention
to that to solve their problems with the proposed system.
According to above
analysis, daily
attendance feature,
overtime calculation and
leave application feature
they hope to add to the
proposed system.
When I consider
the current status
of the existing
payroll system,
most of people
said they are not
satisfied about
the current
system. From
that I can get a conclusion about the system. Some tasks or the activities of the current system is
not totally okay to some employees and some tasks or the activities they satisfied about 50%. So,
we have to identify the weakness points of the system and try to solve that in the proposed
system. These 27 people are very important to us because they know the whole system and they
also know the tasks or activities which needed to be developed. Twelve of people are totally
satisfied about the current system. We can identify the strengths of our current system from
them. So, we can improve the system by their valuable ideas. But eleven of people said they have
no idea about the current system and its’ whole process.
Figure 15
Most of employees are said the attendance sheet of the payroll system need to be developed as
soon as possible because in the current system employees cannot get their monthly attendance
from the current system. It is very important to each employee to get an idea about their
attendance status over the past months. From that chart we can see overtime application and
payroll approval must be developed as they said because it directly effects to their monthly
salary and their yearly bonuses. Also they consider about the pay slip generator in the payroll
system. Due to some technical reasons employees cannot generate their monthly salary slips. So,
we must give the priority to develop these four key areas in our new system.
Most of the employees
said they want to develop
the current overtime
calculation feature in the
payroll system. Same
number of employees
says the monthly salary
slip and total working
Figure 16
hours of the weeks and
months must be included in the proposed system. So, we have to consider these features and their
accuracy than the existing system.