- Information
- AI Chat
ESOFT System Analysis Design Assignment
HND In Computing (HND COM 32)
ESOFT Metro Campus
Recommended for you
Preview text
Higher Nationals
Internal verification of assessment decisions – BTEC (RQF)
####### INTERNAL VERIFICATION – ASSESSMENT DECISIONS
Programme title HND in Computing Assessor Internal Verifier Unit(s) Unit 34: System Analysis & Design Assignment title Automated system for E-Solutions Private Limited Student’s name K Malsha Nimantha Silva 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 Y/N Does the assessment decision need amending? 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
Higher Nationals - Summative Assignment Feedback Form
####### Student Name/ID
####### Unit Title Unit 34: System Analysis & Design
####### 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 D
####### LO2 Produce a feasibility study for a system for a business-related problem
####### Pass, Merit & Distinction
####### Descripts
####### P 2 M
####### LO3 Analyse their system using a suitable methodology.
####### Pass, Merit & Distinction
####### Descripts
####### P 3 M 3 D 2
####### LO4 Design the system to meet user and system requirements.
####### Pass, Merit & Distinction
####### Descripts
####### P 4 M 4
####### Grade: 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.
####### 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” for the left margin of each page.
####### Word Processing Rules
####### 1. The font size should be 12 point, and should be in the style of Time New Roman.
####### 2. Use 1 line spacing. Left justify all paragraphs.
####### 3. Ensure that all the headings are consistent in terms of the font size and font style.
####### 4. 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
####### 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: Date:
####### (Provide E-mail ID) (Provide Submission Date)
E031107@esoft 17 SEPTEMBER 2023
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
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.
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.
M2 Evaluate the relevance of the feasibility criteria on
the systems investigation for the business related problem. LO 1 & LO 2
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
Unit 34
System Analysis & Design
Automated system for E-Solutions Private Limited
K. Malsha Nimantha Silva
Registration No – 00124481
Acknowledgement
I would like to extend my heartfelt gratitude and appreciation to our esteemed lecturer, Mr.
Suchith, who has been a beacon of guidance and support throughout our journey in Systems
Analysis & Design. His unwavering commitment to imparting knowledge and his profound
understanding of various IT subjects have been instrumental in our learning experience.
Undoubtedly, this assignment presented us with numerous challenges and obstacles to
overcome. It's no secret that balancing work commitments and academic responsibilities can
be an arduous task. As I navigated through this demanding period, managing not only this
assignment but also two more submissions scheduled for this same September month, I found
myself facing the daunting specter of stress and time constraints.
In moments when the pressure seemed overwhelming, the support of my friends became
invaluable. We forged a resilient team, each of us contributing our unique strengths and
unwavering determination to the successful completion of this assignment.
I would also like to express my sincere gratitude to our institute, ESOFT, for providing us
with the platform and resources necessary for our academic pursuits.
This assignment has been a journey of challenges, growth, and resilience. It has taught me the
importance of perseverance and the value of a strong support system. As I reflect on this
experience, I am reminded that it is in facing adversity that we truly discover our capabilities.
Once again, thank you, Mr. Suchith, ESOFT, and my friends, for being an integral part of this
educational voyage. Your support has made all the difference, and I am immensely grateful
for it.
Figure Table
Figure 01 - The System Development Life Cycle...........................................................................
Figure 02 - Types of Agile Methodology Approaches
The choice of the most suitable Agile Systems Analysis Methodology hinges on factors such
as project characteristics, team expertise, and organizational culture. It depends on specific
project requirements, including size, complexity, and the desired level of predictability.
Consider team familiarity with Agile practices for the best fit in the project's context and
goals....................................................................................................................................................
Figure 03 - Agile Methodology Life Cycle......................................................................................
Figure 04 - Approach styles of Traditional and Agile System Analysis Methods.....................
Figure 05 - Areas covered by the feasibility study.......................................................................
Figure 06 - This is the Agile methodology structure that I used to do my analysis and review
the system requirements of the proposed CRM system............................................................
Figure 07 - These are the perks that I get by using the Agile Software Development Method
for E-Solution's CRM System Requirements Analysis. In my analysis, I able to cover various
aspects of this project and do a detailed review of it. I think my analysis gets success by
using an Agile Scrum style approach.............................................................................................
Figure 08 - The E-Solutions CRM System Architectural design. This is a holistic blueprint,
intricately weaving user-friendly interfaces, collaborative project management, and robust
data handling. It's a strategic vision that positions the CRM as a transformative force,
aligning seamlessly with E-Solutions' goals for efficiency, collaboration, and sustained
growth...............................................................................................................................................
Figure 09 - Agile methodology is highly effective due to its iterative, adaptive approach,
fostering collaboration, continuous feedback, and rapid response to change, ensuring the
delivery of customer-focused, high-quality solutions in dynamic business environments..
Activity 01
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.
LO1 Evaluate the strengths and weaknesses of the traditional and agile systems analysis
methodologies.
Systems Analysis Methodologies
In the dynamic and ever-evolving landscape of information technology and business
operations, organizations often encounter the need to develop and implement effective
systems to address complex problems, improve efficiency, and meet changing requirements.
This is where Systems Analysis Methodologies come into play.
Systems Analysis Methodologies can be defined as structured and systematic approaches or
frameworks used by organizations to comprehensively examine, design, and implement
systems or solutions tailored to specific needs and challenges. These methodologies provide a
methodical and organized way of understanding the intricacies of complex systems,
identifying and documenting requirements, and subsequently crafting solutions that not only
meet these requirements but do so efficiently and effectively.
Systems analysis methodologies encompass a series of interrelated activities and processes,
each contributing to the successful realization of a system. These activities typically include
Problem Identification
The initial step involves understanding and defining the problem or need that the system aims
to address. It is crucial to have a clear understanding of the challenges at hand before
proceeding.
Requirements Gathering
Collecting and documenting both functional and non-functional requirements, which may
include user needs, constraints, and system capabilities, is a fundamental aspect. This stage
lays the foundation for the entire development process.
System Design
This phase entails creating a detailed blueprint or plan for the system. It includes architectural
design, interface specifications, data flow diagrams, and other technical aspects that define
how the system will function.
Development
With the design specifications in hand, the development phase involves building the actual
system, often involving coding and programming.
Weaknesses
Limited flexibility for changes after a phase is complete.
02 Agile Methodologies (Scrum)
Agile methodologies, such as Scrum, are characterized by iterative and incremental
development. They prioritize collaboration, flexibility, and customer feedback.
Key Characteristics
Development occurs in short iterations (sprints), frequent stakeholder involvement, and
adaptability to changing requirements.
Strengths
Highly adaptable, suitable for dynamic environments, and encourages customer
collaboration.
Weaknesses
May require experienced and self-organizing teams, less emphasis on comprehensive
documentation.
03 Rational Unified Process (RUP)
RUP is a comprehensive, adaptable methodology often used for large-scale software
development projects. It emphasizes iterative development, architecture-driven design, and
risk management.
Key Characteristics
Phases include Inception, Elaboration, Construction, and Transition, each with specific
objectives and activities.
Strengths
Provides a well-defined structure with a focus on architecture and risk management.
Weaknesses
Can be complex and resource-intensive, may not suit smaller projects.
04 Lean Software Development
Lean software development draws inspiration from lean manufacturing principles to
eliminate waste, improve efficiency, and deliver value to customers.
Key Characteristics
Emphasis on reducing waste, continuous improvement, and delivering value as quickly as
possible.
Strengths
Focuses on efficiency and customer value, adaptable to various project types.
Weaknesses
May require cultural and organizational changes.
These methodologies represent a spectrum of approaches to systems analysis and
development, each with its own strengths and weaknesses. In the following sections, we will
delve deeper into the evaluation of traditional and agile systems analysis methodologies to
better understand when and where each may be most effective.
P1 Discuss the strengths and weaknesses of the traditional and agile systems analysis
methodologies
Traditional Systems Analysis Methodology
The Traditional Systems Analysis Methodology, often referred to as the Waterfall model, is a
well-established and sequential approach to systems development that has been widely used
in the field of information technology and software engineering. This methodology is
characterized by its structured and linear progression through distinct phases, each building
upon the previous one, with a primary focus on comprehensive planning and documentation.
But what are the Key Phases of Traditional Systems Analysis Methodology?
Before we dive into the specific phases of the Traditional Systems Analysis Methodology,
let's take a moment to understand the broader framework in which it operates. The
Traditional Systems Analysis Methodology is, in essence, a structured approach embedded
within the larger framework known as the System Development Life Cycle (SDLC).
The System Development Life Cycle (SDLC)
The System Development Life Cycle, often referred to as SDLC, is the comprehensive
framework that guides the entire journey of creating and managing information systems.
Much like a well-structured novel that guides readers through a story, the SDLC provides a
structured path for organizations to follow from the initial concept of a system to its eventual
retirement. It serves as the master plan, ensuring that each phase and activity in the
development process is organized, systematic, and purposeful. The SDLC encompasses every
aspect of system development, from defining requirements and design to implementation,
testing, deployment, and ongoing maintenance. This structured approach not only helps in
achieving successful system outcomes but also ensures that development efforts align with
organizational goals and best practices, leading to efficient and effective results.
ESOFT System Analysis Design Assignment
Course: HND In Computing (HND COM 32)
University: ESOFT Metro Campus
- Discover more from:
