Higher Nationals
Internal verification of assessment decisions – BTEC (RQF)
INTERNAL VERIFICATION – ASSESSMENT DECISIONS
Programme title
HND in Computing
Assessor
Unit(s)
Assignment title
Internal Verifier
Unit 34: System Analysis & Design
Automated system for E-Solutions Private Limited
Student’s name
List which assessment criteria
the Assessor has awarded.
Pass
Merit
Distinction
INTERNAL VERIFIER CHECKLIST
Do the assessment criteria awarded match
those shown in the assignment brief?
Y/N
Is the Pass/Merit/Distinction grade awarded
justified by the assessor’s comments on the
student work?
Y/N
Has the work been assessed
accurately?
Y/N
Is the feedback to the student:
Give details:
• Constructive?
• Linked to relevant assessment criteria?
• Identifying opportunities for
improved performance?
• Agreeing actions?
Y/N
Y/N
Y/N
Does the assessment decision need
amending?
Y/N
Y/N
Assessor signature
Date
Internal Verifier signature
Date
Programme Leader signature (if required)
Date
Confirm action completed
Remedial action taken
Give details:
Assessor signature
Date
Internal Verifier
signature
Date
Programme Leader
signature (if required)
Date
H. A. Dulanjalee Sanjula
Unit 34: System Analysis and Design
1
Higher Nationals - Summative Assignment Feedback Form
Student Name/ID
Unit 34: System Analysis & Design
Unit Title
Assignment Number
1
Assessor
Submission Date
Date Received
1st submission
Re-submission Date
Date Received 2nd
submission
Assessor Feedback:
LO1 Evaluate the strengths and weaknesses of the traditional and agile systems analysis
methodologies
Pass, Merit & Distinction
Descripts
P1
M1
D1
LO2 Produce a feasibility study for a system for a business-related problem
Pass, Merit & Distinction
Descripts
P2
M2
LO3 Analyse their system using a suitable methodology.
Pass, Merit & Distinction
Descripts
P3
M3
D2
LO4 Design the system to meet user and system requirements.
Pass, Merit & Distinction
Descripts
Grade:
P4
M4
Assessor Signature:
Date:
Resubmission Feedback:
Grade:
Assessor Signature:
Date:
Internal Verifier’s Comments:
Signature & Date:
* Please note that grade decisions are provisional. They are only confirmed once internal and external moderation has taken place and
grades decisions have been agreed at the assessment board.
H. A. Dulanjalee Sanjula
Unit 34: System Analysis and Design
2
Pearson Higher Nationals in
Computing
Unit 34: Systems Analysis & Design
Assignment 01
H. A. Dulanjalee Sanjula
Unit 34: System Analysis and Design
3
General Guidelines
1. A Cover page or title page – You should always attach a title page to your assignment. Use
previous page as your cover sheet and make sure all the details are accurately filled.
2. Attach this brief as the first section of your assignment.
3. All the assignments should be prepared using a word processing software.
4. All the assignments should be printed on A4 sized papers. Use single side printing.
5. Allow 1” for top, bottom , right margins and 1.25” for the left margin of each page.
Word Processing Rules
1.
2.
3.
4.
The font size should be 12 point, and should be in the style of Time New Roman.
Use 1.5 line spacing. Left justify all paragraphs.
Ensure that all the headings are consistent in terms of the font size and font style.
Use footer function in the word processor to insert Your Name, Subject, Assignment No, and
Page Number on each page. This is useful if individual sheets become detached for any
reason.
5. Use word processing application spell check and grammar check function to help editing your
assignment.
Important Points:
1. It is strictly prohibited to use textboxes to add texts in the assignments, except for the
compulsory information. eg: Figures, tables of comparison etc. Adding text boxes in the body
except for the before mentioned compulsory information will result in rejection of your work.
2. Avoid using page borders in your assignment body.
3. Carefully check the hand in date and the instructions given in the assignment. Late
submissions will not be accepted.
4. Ensure that you give yourself enough time to complete the assignment by the due date.
5. Excuses of any nature will not be accepted for failure to hand in the work on time.
6. You must take responsibility for managing your own time effectively.
7. If you are unable to hand in your assignment on time and have valid reasons such as illness,
you may apply (in writing) for an extension.
8. Failure to achieve at least PASS criteria will result in a REFERRAL grade .
9. Non-submission of work without valid reasons will lead to an automatic RE FERRAL. You will
then be asked to complete an alternative assignment.
10. If you use other people’s work or ideas in your assignment, reference them properly using
HARVARD referencing system to avoid plagiarism. You have to provide both in-text citation
and a reference list.
11. If you are proven to be guilty of plagiarism or any academic misconduct, your grade could be
reduced to A REFERRAL or at worst you could be expelled from the course
H. A. Dulanjalee Sanjula
Unit 34: System Analysis and Design
4
Student Declaration
I hereby, declare that I know what plagiarism entails, namely to use another’s work and to present
it as my own without attributing the sources in the correct form. I further understand what it means
to copy another’s work.
1. I know that plagiarism is a punishable offence because it constitutes theft.
2. I understand the plagiarism and copying policy of Edexcel UK.
3. I know what the consequences will be if I plagiarise or copy another’s work in any of the
assignments for this program.
4. I declare therefore that all work presented by me for every aspect of my program, will be my
own, and where I have made use of another’s work, I will attribute the source in the correct
way.
5. I acknowledge that the attachment of this document signed or not, constitutes a binding
agreement between myself and Pearson , UK.
6. I understand that my assignment will not be considered as submitted if this document is not
attached to the assignment.
Student’s Signature:
(Provide E-mail ID)
H. A. Dulanjalee Sanjula
Date:
(Provide Submission Date)
Unit 34: System Analysis and Design
5
Higher National Diploma in Computing
Assignment Brief
Student Name /ID Number
Unit Number and Title
Unit 4: Systems Analysis & Design
Academic Year
2021/22
Unit Tutor
Assignment Title
Automated system for E-Solutions Private
Limited
Issue Date
Submission Date
IV Name & Date
Submission format
The submission should be in the form of an individual written report written in a concise,
formal business style using single spacing and font size 12. You are required to make use
of headings, paragraphs, and subsections as appropriate, and all work must be supported
with research and referenced Please provide in-test citations, reference list and
bibliography using Harvard referencing system. Please also provide a bibliography using
the Harvard referencing system.
The recommended word limit is not less than 5000 words, although you will not be
penalised for exceeding the total word limit.
Unit Learning Outcomes:
LO1 Evaluate the strengths and weaknesses of the traditional and agile systems analysis
methodologies.
LO2 Produce a feasibility study for a system for a business-related problem.
LO3 Analyse their system using a suitable methodology.
LO4 Design the system to meet user and system requirements.
H. A. Dulanjalee Sanjula
Unit 34: System Analysis and Design
6
Assignment Brief and Guidance:
*Please note that assignment guidance is for reference only and should be more specific
in detail to meet customized needs.
Assignment brief
Case study
The new automated system is designed to replace the current, manual, error-prone
process of E-Solutions private Limited. The automation of existing process is to reduce the
company’s expenses and enhance the productivity significantly. This transformation also
would support for:
1) Successful teams working
2) Completing projects on time and within budget due to a better understanding of system
requirements and tasks to be completed
3) Starting projects on time through automated project scheduling system.
In the proposed system, the Project director creates a project and a “project profile” for
each project. The creation of the project profile includes identification of project
employee costs, the assignment of tasks to the project, and the assignment of a project
manager. The project profile is consisted of project id, project personnel cost, a list of
tasks assigned, and the project manager. The Project director also creates the teams for
a given project, assigns employees to the teams, and assigns a team leader. The Project
manager is responsible for assigning tasks to various teams working on the projects(s).
The Team Leader assigns tasks to the team members.
Additional functionality includes:

Produce and update information about different software projects, project teams,
specific team member assignments and team skills.

Perform function point analysis to identify the personnel cost of the project and provide
information to generate invoices upon completion of project phases.

Monitor projects and identify completed tasks and ongoing tasks of each project.
Activity 01
H. A. Dulanjalee Sanjula
Unit 34: System Analysis and Design
7
Discuss traditional and agile system analysis methodologies used in the industry by
comparing and contrasting the strengths and weaknesses of them. Critically evaluate two
methodologies by referring to the examples to support your answer.
Activity 2
Produce a feasibility report for the scenario given above and assess the importance of
feasibility criteria used for the system investigation. Critically evaluate the strengths and
weaknesses of feasibility study with relevant to the proposed solution.
Activity 3
Analyse and review the system requirements of the proposed solution given in the
scenario using a suitable methodology. Functional and non-functional requirements of
the system should be clearly mentioned. Assessment of the effectiveness and suitability
of the chosen methodology should be provided with proper justifications.
Activity 4
Produce a system design specification for the above scenario and assess the effectiveness
of your design and the methodology used with reference to how it meets the user
requirements.
Your system design specification should include architectural design, interface design,
database design, and program design.
H. A. Dulanjalee Sanjula
Unit 34: System Analysis and Design
8
H. A. Dulanjalee Sanjula
Unit 34: System Analysis and Design
9
Table of Contents
Abbreviations ...................................................................................................................................................... 11
Acknowledgement .............................................................................................................................................. 12
List of Figures ...................................................................................................................................................... 13
List of Tables ....................................................................................................................................................... 14
Introduction ........................................................................................................................................................ 15
Conclusion ................................................................................................. Ошибка! Закладка не определена.
References .......................................................................................................................................................... 32
H. A. Dulanjalee Sanjula
Unit 34: System Analysis and Design
10
Abbreviations
H. A. Dulanjalee Sanjula
Unit 34: System Analysis and Design
11
Acknowledgement
H. A. Dulanjalee Sanjula
Unit 34: System Analysis and Design
12
List of Figures
H. A. Dulanjalee Sanjula
Unit 34: System Analysis and Design
13
List of Tables
H. A. Dulanjalee Sanjula
Unit 34: System Analysis and Design
14
Introduction
H. A. Dulanjalee Sanjula
Unit 34: System Analysis and Design
15
Discuss traditional and agile system analysis methodologies used in the industry by comparing and
contrasting the strengths and weaknesses of them. Critically evaluate two methodologies by referring to
the examples to support your answer.
Traditional methodology
Traditional methodologies are based on a software development lifecycle with several pre-defined phases.
The phases are organized in unidirectional way as one phase after another. The current phase must be
completed in order for the next phase to begin and each phase has defined deliverables. The phases of the
traditional approach are initiation, planning, execution, monitoring and control and closure. Most popular
traditional methodology use in the industry is “waterfall methodology”. In that, the development is starts
from requirements to design and then to development, then to testing and maintenance. Apart from that,
“Phototyping” and “Spiral” are two of the traditional methodologies.
Waterfall model
Strengths of the Traditional methodology
1. Traditional approaches are suited when requirements are well defined and can be understood
upfront of the project. Further the solution also needs to be defined in advance,
2. Has clearly defined objectives/Directions - Since all the planning is done upfront of the project, the
project team knows what activities they need to perform, what are the delivery time lines and
deliverables of the project. The tendency to change in the middle of the project is minimal.
3. Cost effective & more suitable for fix budget projects - Since scope is well defined and estimates can
be established at the beginning of the project easily.
H. A. Dulanjalee Sanjula
Unit 34: System Analysis and Design
16
4. Clear documentation – Traditional approaches uses standard set of project documents, and they
will be used throughout the project life cycle,
5. Suitable for geographically distributed (remote) projects. Since all the project activities, designs and
deliverables are well planned and documented, it is relatively easy for developers to work in a
remote place.
6. Sequential project phases make easy for developers and testers to understand and execute project
activities.
Weaknesses of the Traditional methodology
1. The customer can only see the product at the end of the development and the is no way to conduct
intermediate evaluations. That could lead to deviation of customer expectations
2. Resistant to change – It is difficult to introduce changes at the middle of the project. Since project is
planned upfront and each phase is organized in sequential/linear order, introducing changes is very
costly and difficult.
3. Deviation from customer expectation – The system is developed based on the developer’s
understanding and this might not always meet the customer’s needs.
4. Late testing -In the traditional approach, testing can begin only after the development process is
finished. Any correction or amendment could have made a significant impact on project cost and
delivery timelines.
5. In traditional approach, extensive documentation is required, and the team has to put a
considerable for documentation.
Agile methodology
Agile is an iterative and incremental development approach. This is more customer friendly software
development approach, and it is flexible for changes throughout the development phase. Scrum, Kanban,
Extreme Programming (XP), Lean development are some of the popular agile approaches. Agile
methodology focuses more on teamwork, collaboration, flexibility, and incremental delivery rather than
delivering the whole software at once. An agile approach is best suited for projects which requirements are
ambiguous and progressively elaborate throughout the project.
Scrum methodology
Scrum is a project management framework that provides a structure for fast-paced Agile teams to
prioritize, manage, and execute work. Scrum projects execute as time boxed iterations called “Sprints “.
Each Sprints last 1 to 4 weeks and at the end of it produces a usable software deliverable. Scrum
framework defines several roles as Product Owner, Scrum Master and the development team, The product
owners job is to ensure that the interests of the stakeholders and customers are represented through the
project. Scrum master is a facilitator to the team and scrum team is a cross functional team. The team has
all the required skills to do the intended work.
Scrum framework has two artifacts called product the backlog and the sprint backlog. The prodc=uct
H. A. Dulanjalee Sanjula
Unit 34: System Analysis and Design
17
Strengths of the Agile methodology
1. More focus on customer satisfaction than following processors.
2. Agile development methodology is flexible to change, and requirement can be modified at any time.
3. Fast and frequent delivery - The client get opportunity to experience the product at the early stage
due to incremental delivery
4. Due to continuous client involvement, he can determine whether the final product meets his
business goal.
5. Agile uses relatively less documentation and more focus on final product.
6. Direct face to face team communication provides better understanding of objectives and tasks.
7. Highly skilled cross- functional teams helps to provide better results.
Weaknesses of Agile methodology
1. There is a lack of necessary designing and planning documentation
2. It is difficult to apply for geographically distributed large projects
3. It requires an expert project member to take crucial in the meeting.
4. The project can go off the track if the Product Owner isn't clear what the end result that client need.
Traditional
vs.
Agile
Software
Development
Methodologies
2018
by
Indusree
https://www.kpipartners.com/blog/traditional-vs-agile-software-development-methodologies
ReQtest. 2021. Agile Software Development and Requirements
https://reqtest.com/agile-blog/requirements-in-agile-software-development/.
H. A. Dulanjalee Sanjula
Unit 34: System Analysis and Design
18
Mavuru,
Strength and the Weaknesses of Traditional and
Agile Methodologies
Parameter
Development Approach
Customer Involvement
Suitability of Project size and
complexity
User Requirements
Project Communication
Documentation
Project Plan
Traditional Methodology
Linear
Low
Suitable for large scale more
complex projects
Should be defined and finalized
at the beginning of the project
Formal Communication
Require comprehensive project
documentation
Well document project plan
Deliverables/release
One time delivery at the end of
the project
Adopting changes
Difficult
Agile Methodology
Iterative and incremental
High
Suitable for small and medium
scale projects
Requirements are progressively
elaborated during each iteration
Informal direct communication
with team members are
encouraged
Minimum documentation
required
No formal project plan like in
traditional approach
Incremental feature wise
delivery at the end of each
iteration
Easy
Activity 2
Produce a feasibility report for the scenario given above and assess the importance of feasibility criteria
used for the system investigation. Critically evaluate
feasibility study for a system for a business- related problem
Produce a feasibility report for the scenario given above and assess the importance of feasibility criteria
used for the system investigation.
H. A. Dulanjalee Sanjula
Unit 34: System Analysis and Design
19
Feasibility is a measure of how well a proposed system solves the intended problem/problems by analysing
all the related factors including economic, technical, legal, and scheduling considerations in order to
determine the project's chances of success. That basically provide an assessment whether the system is
worthwhile to deploy and if it can be implemented within the existing budget and timeline. The outcome of
the feasibility study will be compiled into a document called feasibility report which provide executive
management of a company to take decision on a project’s viability. In certain situations, such as project
cost exceed the planned budget, technical barriers that cannot be overcome, legal issues etc., project many
are not viable to execute and could be wise to abandon the project.
Types of Feasibilities
There are several types of feasibility studies, each make different level of impact to a project.
i.
ii.
iii.
iv.
v.
Economic feasibility
Technical feasibility
Operational feasibility
Legal feasibility
Schedule feasibility
Economic feasibility
The economic feasibility describes the cost-benefit analysis of the project, which helps organizations in
determining the project's viability from financial perspective. This assessment also provides an
independent assessment and enhances project implementation credibility by assisting decision-makers to
determine the proposed project's benefits to the organization from the economic positive.
Technical feasibility
The area of feasibility study determines whether the technical resources available are sufficient for the
project and whether the technical resources are capable of implement the proposed system. This
evaluates available the technical resource and their competencies against the proposed project technical
requirements. That includes the proposed system's hardware, software, and other technical needs.
Operational feasibility
This is a measure of how well a proposed system solves the problems of the client or and how well—the
project can meet the organization's needs. This is also look at how a project plan meets the requirements
specified during the system development requirements analysis phase.
Legal feasibility
This is an assessment of the proposed project against violation of regulations or legal boundaries. There are
several factors such as data protection acts, social media laws, government security related lows etc. Foe
example as per Sri Lankan low bank transaction related data should be preserved for 15 years in case of
any legal requirement before they can be purged.
H. A. Dulanjalee Sanjula
Unit 34: System Analysis and Design
20
Schedule feasibility
This is a measure of whether the project can be completed within expected duration. An organization
estimates the amount of time it will take to execute a project when scheduling feasibility.
`
Importance of Feasibility Study
By performing a feasibility, an organization can get an assessment of success of a project before investing
resources, time or money. It helps executive management of an organization to make critical decision in
time before getting too late recover. A feasibility study could uncover new ideas that change the scope of a
project in better way.
Following are some of the key benefits of performing a feasibility study
i.
ii.
iii.
iv.
v.
vi.
Help to make decision ahead of time
Provides critical information for a “go/no-go” decision of a proposed project
Identify better solution approaches’
Reduce project associated risks
Improve project success rare
Identify key benefits and disadvantages of a proposed project
Feasibility Analysis - Apppm. 2021. Feasibility Analysis - Apppm.
http://apppm.man.dtu.dk/index.php/Feasibility_Analysis.
Feasibility Report
Automated Project Management System for E-solutions private limited.
Introduction
This feasibility report evaluated the implementation feasibility of the proposed Automated Information
Management System at E-solutions private limited
Project Details
Budget –LKR 1,000,000.00
Schedule Duration – 6 months
Technical Feasibility
The proposed is a web-based application which uses will be able to access through commonly available
web browsers such as Google Chrome, Microsoft Edge, Firefox etc. The application will be hosted on
premisses in local servers. Existing LAN infrastructure is sufficient for the connectivity. The system will
not be exposed to the internet.
The development team has all the required technical competences to implement the system
Infrastructure
H. A. Dulanjalee Sanjula
Unit 34: System Analysis and Design
21
Existing hardware infrastructure is insufficient for hosting the application and new server environment is
required for web server and the database server.
Operational feasibility
The requirement specification of the proposed system addresses all the E-solutions private Limited’s
workflow requirements and employees should be given an adequate system training ones it is
implemented.
Legal feasibility
The system has the capability to retain the E-solutions private Limited’s project related data as per the
respective client agreement.
Economic feasibility
Assessment of the cost components as follows
Cost Item
Development cost
Software licensing cost
Hardware cost
Miscellaneous cost
Total
Value (LKR)
550.000
200,000
325,000
100,000
1,175,000
Strengths and Weaknesses of Feasibility study
Strengths
i.
It helps stakeholders to identify pros and cons of the proposed project in time.
ii.
Feasibility study provide valuable insight to investors that could help them to take correct
business
iii.
Feasibility study can help identifying project risks and potential contingency approaches.
iv. Feasibility studies also help companies with new business development, including determining
how it will operate, potential obstacles, competition, markets analysis, and the mount and source
of financing needed to grow the business.
Weaknesses
i.
Since the study carried out by collecting information rather than address real practical situation,
the feasibility outcome may result fault decision making
ii.
This is time consuming and costly activity.
H. A. Dulanjalee Sanjula
Unit 34: System Analysis and Design
22
Activity 3
Analyse and review the system requirements of the proposed solution given in the scenario using a suitable
methodology. Functional and non-functional requirements of the system should be clearly mentioned.
Assessment of the effectiveness and suitability of the chosen methodology should be provided with proper
justifications
Functional Requirements
Descriptions of required product features or facilities of a proposed system called functional requirements.
These requirements represent system provided facilities for users. Functional requirements describe
system behaviour under specific conditions.
Eg: Project Director at E-solutions private limited want to create a project in the system
It is necessary for both development team and stakeholders to have clear and detail understand of
functional requirement otherwise the completed system may not fulfil the client needs.
Functional Requirements of a system should include the following things:
i.
ii.
iii.
iv.
v.
vi.
Details of operations conducted in every screen
Data handling logic should be entered into the system
It should have descriptions of system reports or other outputs
Complete information about the workflows performed by the system
It should clearly define who will be allowed to create/modify/delete the data in the system
How the system will fulfil applicable regulatory and compliance needs should be captured in the
functional document
Non-functional Requirements
H. A. Dulanjalee Sanjula
Unit 34: System Analysis and Design
23
Non-functional Requirements specifies the quality attribute
of a software system. They judge the software system based
on Responsiveness, Usability, Security, Portability and other non-functional standards that are critical to
the success of the software system.
Eg : Each web page must load within 2 seconds.
Non-functional requirements for the new system can be consider as limits, goals or control mechanisms.
They describe how well or by what standard the proposed system should operate. For example, particular
system should be able to process 100 transactions per minute. Therefore. It is essential to pay much
attention to non-functional requirements same as functional requirements at system analysis stage.
Assessment of the effectiveness and suitability of the chosen methodology should be provided with
proper justifications.
Product Quality
The Agile methodologies provide better product quality in software developing by,
i.
ii.
iii.
iv.
v.
vi.
vii.
viii.
ix.
Focus on continuous improvement at the end of each sprint by conducting a retrospective
Defining and elaborating requirements in a timely manner so that knowledge of product features
is as relevant as possible
Embracing technological excellence, better design, and sustainable development techniques
Continuous integration and testing of product increments
Maintaining better communicating within the team
Take advantage of automated testing tools, develop during the day, test overnight and debug in
the morning
Continuous customer engagement and product demonstration to client at the end of each sprint
Due to parallel development and testing, it is easy to fix bugs and defects
Having а product owner who is an expert of the product requirements and customer’s needs
Motivated team
Agile team is a self-organizing and cross-functional team. Being а part of а self-governing team allows
people to become creative, innovative, and facilitate to build multi discipline skills within them. To protect
the team from external influences and impediments, there is a scrum master. Team maintain good
collaboration with each other and continuous communication within them members as well as product
owner and clients are encourage in agile methodology.
Better performance visibility
In Agile environment, every member of the team have an opportunity to get an idea about how things
going on the project at any given time. Daily scrum, progress charts and visual boards offer visibility of the
Project status.
H. A. Dulanjalee Sanjula
Unit 34: System Analysis and Design
24
Agile Team Structure
Agile team contain limited number of team members. It is a cross functional team and they have all
competencies needed to accomplish their work without depending on others that are not part of the team.
Improved Predictability
Agile methodology has several best practices, artifacts, and tools to improve project predictability, that
includes
i.
Time boxed sprints with identical length trough out the project lifecycle gives an idea of cost per
sprint
ii.
Agile team velocity allows the project team to determine timeline and budgets for releases, the
remaining product backlog
iii.
Using the knowledge from daily scrum meetings, sprint burn down chart, and task boards, the
project team can determine the performance of each sprint.
Reduced Project Risk
Agile methodology reduces the project risk by,
i.
Developing in sprints, ensuring а brief time between initial project investment and either falling
fast or knowing that а product or an approach will work
ii.
Always having а working product, starting with the very first sprint, so no agile project fails
completely
iii.
Developing requirements to the definition of worn out each sprint in order that project sponsors
have completed, usable features, irrespective of what may happen with the project within the
future
iv. Providing constant feedback on products and processors through daily scrum meetings and
constant development team communication, sprint reviews and retrospectives, and releases
during which the tip user can see and react to new features on а daily basis
v.
Generating revenue early with self-funding projects, allowing organizations to get hold of а project
with little upfront expense
(Wiley, 2021)
Activity 4
Produce a system design specification for the above scenario and assess the effectiveness of your design and
the methodology used with reference to how it meets the user requirements.
Your system design specification should include architectural design, interface design, database design, and
program design.
System Design
H. A. Dulanjalee Sanjula
Unit 34: System Analysis and Design
25
Systems design is the process of defining technical elements
of the proposed software system including modules, system
architecture, components, user interfaces, integration points, database specification and other key
technical concerns.
Design Specification Document
The design specification document specifies in-depth descriptions of the software that will be developed
including architecture of the proposed system, components are to be implemented, database design,
proposed system interfaces etc. The design speciation is usually written by a senior technical person in the
project team such as software architect or technical lead. This document considered as the key technical
reference source of the project team throughout the project life cycle. The software design document
helps to ensure the design specifications of the software are well understood and clear to the project team.
Software Design Specification of Automated Project Detail Management System for E-Solutions private
Limited
1. Introduction
This document describes the Detailed Technical Design of the Automated Project Detail Management
System including system architecture sub-systems, components and their associated interfaces, database
schemas, design goals and the motivations behind the chosen design. Both high-level and low-level designs
are included in this document.
This document should be read by an individual with a technical background and has experience reading
data flow diagrams, control flow diagrams, interface designs, and technical specifications.
2. Design Considerations




Provide user friendly robust application
Meet customer defined system performance goals
Meet customer defined system security goals
Provide reliable and extensible system
3. Architecture Design
H. A. Dulanjalee Sanjula
Unit 34: System Analysis and Design
26
Architectural Design provides the overall view of the system
including its subsystems that are derived from analysis packages in the requirement model. Software
development projects seeking rapid, sustainable delivery are combining agile and architecture practices to
manage competing goals of speed in the short term and stability over the long term.
Architecture Diagram
Draw this again
A Collaborative Project Management Architecture, Fang Chen, Jay F. Nunamaker, Jr, Nicholas C. Romano,
Jr.Robert O. Briggs 2003
https://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.2.5752&rep=rep1&type=pdf
H. A. Dulanjalee Sanjula
Unit 34: System Analysis and Design
27
Component Diagram
The component diagram illustrates the structural relationships between the components and their
interfaces
Draw this again
Interface Specification
https://www.researchgate.net/figure/System-Modules-for-Prototype-Collaborative-Project-ManagementSoftware_fig1_221180626
H. A. Dulanjalee Sanjula
Unit 34: System Analysis and Design
28
H. A. Dulanjalee Sanjula
Unit 34: System Analysis and Design
29
H. A. Dulanjalee Sanjula
Unit 34: System Analysis and Design
30
Re draw all above
Justify the choice of the analysis methodology used in the context of the business problem. Why use
Agile Methodology?
System Design Approach
Agile Design methodology has been used for designing the system. Agile uses an iterative design process
starts from first stage and moves towards last stage. Then the output is analysed, and multiple iterations
are run to further improve it. In agile design process, the stages run in parallel. You divide the functionality
into small parts that can be delivered independently and start working on them. This helps to make faster
design and get quick feedback of work.
The agile design approach has following characteristics,
1. Quick Feedback: It becomes easier to know timely that what customer wants, instead of providing
him a complete prototype and then ask for feedback.
2. Change Management: Changes in design becomes easier and cheaper. No waste of time and
money.
3. Faster Development: Delivering small chunks of design to development team also enables faster
implementation. Development team does not wait for the complete design to start its
implementation
H. A. Dulanjalee Sanjula
Unit 34: System Analysis and Design
31
Due to above listed reasons agile analysis method was used
to designing the Automated Project Management System at
E-solutions private limited.
Agile-Design Process, Maria Chebyniak 2019
https://m-cheba.medium.com/agile-design-process-81cf159d0359
References
There are no sources in the current document.
A Collaborative Project Management Architecture, Fang Chen, Jay F. Nunamaker, Jr, Nicholas C. Romano,
Jr.Robert O. Briggs 2003
https://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.2.5752&rep=rep1&type=pdf
Feasibility Analysis - Apppm. 2021. Feasibility Analysis - Apppm.
http://apppm.man.dtu.dk/index.php/Feasibility_Analysis.
ReQtest. 2021. Agile Software Development and Requirements
https://reqtest.com/agile-blog/requirements-in-agile-software-development/.
Agile-Design Process, Maria Chebyniak 2019
https://m-cheba.medium.com/agile-design-process-81cf159d0359
Collaborative Project Management Software , Nicholas Romano
https://www.researchgate.net/figure/System-Modules-for-Prototype-Collaborative-Project-ManagementSoftware_fig1_221180626
H. A. Dulanjalee Sanjula
Unit 34: System Analysis and Design
32
H. A. Dulanjalee Sanjula
Unit 34: System Analysis and Design
33
Grading Criteria
Achieved
Feedback
LO1 Evaluate the strengths and weaknesses of the
traditional and agile systems analysis methodologies.
P1 Discuss the strengths and weaknesses of the traditional
and agile systems analysis methodologies.
M1 Compare and contrast the strengths and weaknesses of
the traditional and agile systems analysis methodologies.
LO2 Produce a feasibility study for a system for a
business-related problem.
P2 Produce a feasibility study for a system for a
business related problem.
H. A. Dulanjalee Sanjula
Unit 34: System Analysis and Design
34
M2 Evaluate the relevance of the feasibility criteria on
the systems investigation for the business related
problem.
LO1 & LO2
D1 Critically evaluate the strengths and weaknesses of the
traditional and agile methodologies and feasibility study.
LO3 Analyse their system using a suitable
Methodology
P3
Review a system using a suitable methodology for a
business-related problem.
M3
Analyse the effectiveness of the methodology used in
providing a solution for a given business context.
LO4 Design the system to meet user and system
Requirements
H. A. Dulanjalee Sanjula
Unit 34: System Analysis and Design
35
P4 Design a fully functional system to meet user and
system requirements for the business related
problem.
M4 Assess the effectiveness of the system design with
reference to the methodology used and how the design
meets user and system requirements.
LO3 & LO4
D2 Justify the choice of the analysis methodology used in
the context of the business problem.
H. A. Dulanjalee Sanjula
Unit 34: System Analysis and Design
36