Cse4004writ1 Aug 2024
Cse4004writ1 Aug 2024
Cse4004writ1 Aug 2024
Assessment
Brief
Module Code Module Title
CSE4004 System Analysis & Designing
Content
Assessment Details....................................................2
Submission Details.....................................................3
Assessment Criteria...................................................3
Further Information.....................................................5
Who can answer questions about my assessment?............5
Referencing..............................................................................5
Submission problems.............................................................5
Unfair academic practice........................................................5
How is my work graded?........................................................6
2
Assessment Details
Assessment title Abr. Weighting
System Analysis & Designing for organization WRIT1 100%
Pass marks are 40% for undergraduate work and 50% for postgraduate work unless stated otherwise.
Task/assessment brief:
Scenario and Tasks
System Analysis & designing is a very important subject domain related to Information systems.
Information systems’ durability, Validity, efficiency & accuracy depends on how well the system
investigation & designing activities are accomplished during the system development life cycle. Learning
& making use of the best tools such as Entity Relationship Diagram, Data Flow Diagram, Flowchart and
Unified Modelling Language Diagrams for aforementioned activities are very much essential for a system
analyst.Clear understand ability of Software Development Life Cycle model stages & unique duties
assigned to those enables software development team to maintain product quality, track progress, project
budget and the nature of the product, according to higher satisfactory level.Selecting the best Software
development process model for an information system project is crucial since success or failure of the
product can be decided by the process model & its systematic approach.When the subject domain is
concerned it is always imperative to attention to be paid in applying creativity and innovation for system
designing in a manner that modern world man kind’s requirements are supported by considering not only
how their lives are further improved with sophistication but also focusing on how does ethical and
professional issues are mitigated as much as possible.
1. You are required to select a company which is related to the given scenario then provide clear
introduction about the organization and then conduct an organizational analysis and use
appropriate fact gathering techniques for gather system requirement of a client (LO3 - 25 Marks)
2. Identify the advantage of using a standard software development lifecycle a model for developing
the software solution what is proposed for the organization/ institution. (LO2- 15 Marks)
3. Design the data model of the software solution that will be implemented in the organization /
institution by considering all required data / information requirements and explain briefly what is
the best technique is to carry out data model designing of the system. (LO4- 25 Marks)
(Should Used Chen's Notation)
4. Design the functional model of the system software solution that will be implemented in the
organization / institution having concerned all the features /facilities, data collection, transitions,
transfers and dissemination requirements and explain briefly what is the best technique is to carry
out functional model designing of the system. (Use case ,class ,Sequence,DFD Diagram context ,
level 0 ,level 1 (LO1 & LO4 35 Marks)
Version 1:
3
Tasks
LO1: Demonstrate system designing methodologies, tools and the techniques
Context Diagram: Provides a high-level view of the system.Shows the system as a single process
and its interactions with external entities.
Level 0 Diagram: Provides more detailed view of the system by breaking down the single process
from the Context Diagram into sub-processes.
Level 1 Diagram: provides more detailed breakdown of the system compared to the Level 0 DFD.
It decomposes one of the processes from the Level 0 diagram into smaller sub-processes,
showing more granular data flows and interactions.
Class diagram: is a type of static structure diagram in the Unified Modeling Language (UML) that
describes the structure of a system by showing its classes, attributes, methods, and the
relationships among objects. It is a fundamental part of object-oriented modeling and is used
extensively in software engineering for designing and documenting software systems.
Sequence Diagram: sequence diagram is a type of interaction diagram in the Unified Modeling
Language (UML) that shows how objects interact in a particular sequence of events. It
emphasizes the time order of messages sent between objects. Sequence diagrams are useful for
visualizing the flow of logic within a system in a step-by-step manner.
Submission Details
Submission This will be provided This will normally be 20
Estimated Feedback
Deadline: on the Moodle working days after initial
submission point. Return Date submission.
4
Time: deadline day.
Moodle/Turnitin: Any assessments submitted after the deadline will not be marked and will be
recorded as a non-attempt unless you have had an extension request agreed
or have approved mitigating circumstances. See the School Moodle pages for
more information on extensions and mitigating circumstances.
File Format: The assessment must be submitted as a pdf document (save the document as
a pdf in your software) and submit through the Turnitin submission point in
Moodle.
Feedback Feedback for the assessment will be provided electronically via Moodle. Feedback will
be provided with comments on your strengths and the areas which you can improve.
View the guidance on how to access your feedback.
All marks are provisional and are subject to quality assurance processes and
confirmation at the programme Examination Board.
Assessment Criteria
Learning outcomes assessed
Demonstrate system designing methodologies, tools and the techniques
Evaluate different systems development life cycle models
Analyze the system by using appropriate fact-finding techniques.
Design the system by using appropriate system design techniques.
Technical Skills
Communication and Interpersonal Skills
Creative and Critical Thinking
5
Marking/Assessment Criteria
• Use of
standard level
(Open
Ended/Close
Ended)
Questionnaire or
Interview Guide.
• Samples of the
Questionnaire &
Interviews
attached.
6
(0-3) (04-07 ) (08-11) (12-15)
02.
System At least Five stages At least Five At least Five
explaination of Development life of the System stages of the stages of the
System cycle explained Development life System System
such as cycle explained Development life Development life
Development Communication, such as cycle explained cycle explained
life cycle planning, Communication, such as such as
Designing, planning, Communication, Communication,
Development & Designing, planning, planning,
Testing, Development & Designing, Designing,
Implementation Testing, Development & Development &
but no mapping Implementation. Testing, Testing,
has been done Implementation. Implementation
with system • Every stage has
implemented. been mapped with • Every stage . • Every stage
proposing system has been mapped has been
development & with proposing mapped with
designing activities. system proposing system
development & development &
• Standard designing designing
documentation by activities. activities.
including Harvard
referencing • The description • The description
based on based on
Prescriptive, Prescriptive,
Incremental, Incremental,
Evolutionary, Evolutionary,
Agile & Agile &
Specialized Specialized
Process Models Process Models •
Justifications
• Standard have been done
documentation by based on the
including Harvard qualities of the
referencing proposing
system.
• Standard
documentation by
including Harvard
referencing
7
illustrated. Relationships & Relationships &
Cardinalities Cardinalities
properly selected properly selected
& illustrated. • & illustrated.
Write a data
dictionary for the
ER diagram. • Write a data
dictionary for the
ER diagram.
• Has been used
standard format
for the Data
dictionary.
04) UML (0-8) (9-17) (18-26) (27-35 )
Diagrams
Draw context Draw context level Draw context Draw context
level Data Flow Data Flow Diagram level Data Flow level Data Flow
Diagram to to illustrate Diagram to Diagram to
illustrate functional model of illustrate illustrate
functional model the proposing functional model functional model
of the proposing system. of the proposing of the proposing
system with some • External Entitles, system. system.
errors. Main Information • External • External
System & Entitles, Main Entitles, Main
Information Initial Information Information
flow between System & System &
External Entities & Information Initial Information Initial
Main Information flow between flow between
System have been External Entities External Entities
identified & & Main & Main
illustrated. Information Information
• Proper Process & System have System have
data flow labeling been identified & been identified &
used illustrated. illustrated.
• Standard • Draw Level 0 • In order to
documentation by Data Flow further explain
including Harvard Diagram to internal logic of
referencing illustrate the major
• Drawing USE functional model processes of the
CASE diagram by of the proposing information
identifying relevant system. showing system,
actors and functions at least five Structured
different English, Decision
transaction Trees & Decision
processors Tables properly
• External used for DFD
Entities, Major level 0
Processes, Data processes.
Storages & initial • Process
Data Flows & specifications
Intermediate Data have been
Flows in between included using
them have been standard process
Identified & specification
illustrated. format
• Object type,
• Draw a Level 1 Data Type, Data
Data Flow Inflow & Data Out
Diagram to Flow have been
illustrate Described
functional model . • Write a data
of the proposing dictionary for the
system DFD level 0 using
considering standard format.
• Top down
8
detailed analysis. designing
• External technique & the
Entities, Sub bottom up
Processes, Data designing
Storages & initial technique should
Data Flows & be properly
Intermediate Data explained
Flows in between considering the
them have been functional design.
Identified & • Drawing USE
illustrated. CASE diagram,
• Proper Process Sequence
& data flow Diagram by
labeling used identifying
• Drawing USE relevant actors
CASE and functions and
diagram ,Sequen identifying
ce Diagram by dependencies
identifying properly (Extend/
relevant actors Include)
and functions and • Drawing Class
identifying diagram by
dependencies identifying all the
properly (Extend/ classes and the
Include) different types of
• Drawing an suitable
average level relationships
Class diagram by among the
identifying several classes
classes related to
the given
scenario.
9
Further Information
Who can answer questions about my Technical submission problems
assessment?
It is strongly advised that you submit your
Questions about the assessment should be work at least 24 hours before the deadline to
directed to the staff member who has set the allow time to resolve any last minute
task/assessment brief. This will usually be the problems you might have. If you are having
Module Leader. They will be happy to answer issues with IT or Turnitin you should contact
any queries you have. the IT Helpdesk on (+44) 2920 417000. You
may require evidence of the Helpdesk call if
Staff members can often provide feedback on you are trying to demonstrate that a fault with
an assignment plan but cannot review any Moodle or Turnitin was the cause of a late
drafts of your work prior to submission. The submission.
only exception to this rule is for Dissertation
Supervisors to provide feedback on a draft of Extensions and mitigating circumstances
your dissertation.
Short extensions on assessment deadlines
Referencing and independent learning can be requested in specific circumstances. If
you are encountering particular hardship
Please ensure you reference a range of
which has been affecting your studies, then
credible sources, with due attention to the
you may be able to apply for mitigating
academic literature in the area. The time
circumstances. This can give the teachers on
spent on research and reading from good
your programme more scope to adapt the
quality sources will be reflected in the quality
assessment requirements to support your
of your submitted work.
needs. Extensions and mitigating
circumstances policies and procedures are
Remember that what you get out of university
regularly updated. You should refer to your
depends on what you put in. Your teaching
degree programme or school Moodle pages
sessions typically represent between 10%
for information on extensions and mitigating
and 30% of the time you are expected to
circumstances.
study for your degree. A 20-credit module
represents 200 hours of study time. The rest
Unfair academic practice
of your time should be taken up by self-
directed study. Cardiff Met takes issues of unfair practice
extremely seriously. The University has
Unless stated otherwise you must use the procedures and penalties for dealing with
HARVARD referencing system. Further unfair academic practice. These are
guidance on referencing can be found in the explained in full in the University's Unfair
Study Smart area on Moodle and at Practice regulations and procedures under
www.citethemrightonline.com (use your Volume 1, Section 8 of the Academic
university login details to access the site). Handbook. The Module Leader reserves the
Correct referencing is an easy way to right to interview students regarding any
improve your marks and essential in aspect of their work submitted for
achieving higher grades on most assessment.
assessments.
10
Types of Unfair Practice, include: Collusion, which can be defined as when
work that that has been undertaken with
Plagiarism, which can be defined as using others is submitted and passed off as solely
without acknowledgement another person’s the work of one person. Modules will clearly
words or ideas and submitting them for identify where joint preparation and joint
assessment as though it were one’s own submission are permitted, in all other cases
work, for instance by copying, translating they are not.
from one language to another or Fabrication of data, making false claims to
unacknowledged paraphrasing. Further have carried out experiments, observations,
examples include: interviews or other forms of data collection
Use of any quotation(s) from the and analysis, or acting dishonestly in any
published or unpublished work of other other way.
persons, whether published in textbooks,
articles, the Web, or in any other format, How is my work graded?
where quotations have not been clearly
identified as such by being placed in Assessment grading is subject to thorough
quotation marks and acknowledged. quality control processes. You can view a
Use of another person’s words or ideas summary of these processes on the
that have been slightly changed or Assessment Explained Infographic.
paraphrased to make it look different from
the original. Grading of work at each level of Cardiff Met
Summarising another person’s ideas, degree courses is benchmarked against a set
judgments, diagrams, figures, or of general requirements set out in Volume 1,
computer programmes without reference Section 4.3 of our Academic Handbook. A
to that person in the text and the source simplified version of these Grade Band
in a bibliography/reference list. Descriptors (GBDs) with short videos
Use of assessment writing services, explaining some of the academic terminology
essay banks and/or any other similar used can be accessed via the Facilitation of
agencies (NB. Students are commonly Learning resource page.
being blackmailed after using essay
mills). We would strongly recommend looking at the
Use of unacknowledged material Study Smart area of Moodle to find out more
downloaded from the Internet. about assessments and key academic skills
Re-use of one’s own material except as which can have a significant impact on your
authorised by your degree programme. grades. Always check your work thoroughly
before submission.
11