Sei sulla pagina 1di 15

Assignment Cover Sheet

Qualification Module Number and Title


Higher National Diploma in Computing & SEC4203
System Development System Analysis & Designing
Student Name & No. Assessor
<to be filled by the student> Mr.Deshan Bulathsinghala
Hand out date Submission Date

12/02/2019 30/03/2019
Assessment type Duration/Length of Weighting of Assessment
Coursework Assessment Type 100%

Learner declaration

I, ………………………………………….<name of the student and registration number>,


certify that the work submitted for this assignment is my own and research sources are fully
acknowledged.

Marks Awarded
First assessor

IV marks

Agreed grade

Signature of the assessor Date


FEEDBACK FORM

INTERNATIONAL COLLEGE OF BUSINESS & TECHNOLOGY


Module:
Student:
Assessor:
Assignment:

Strong features of your work:

Areas for improvement:

Marks Awarded:
Coursework

Learning outcomes covered

1. Understand system designing methodologies, tools and the techniques


2. Evaluate different systems development life cycle models
3. Be able to perform a systems investigation
4. Be able to design a solution using appropriate system design methodologies, tools and the
techniques

Scenario and Tasks

Introduction

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.
Scenario
A software development company is in need of a web based Time Management System for its
executive staff to easily manage their appointments and schedule their meetings.
Each executive has a personal calendar consisting of Calendar Entries where he/she maintains
his/her daily appointments. Each entry has the date, description about the appointment, venue (if
any), and start and end times. Planned vacations of each executive are also marked in the calendar
and each executive is responsible for maintaining this information. There is a secretary in-charge
of the conference rooms.
There are a number of conference rooms available for having meetings/presentations. Each
conference room has a specific capacity and different facilities such as overhead projectors
installed, video conferencing capabilities etc. A calendar of its own is there for each room which
can be used to view its availability or unavailability status, duration of bookings and also who has
booked it for each time slot.
The system should provide a facility to view Calendars of any executive and conference rooms
and thereby book a meeting for any available time slot in any day. The anticipated practice would
be to pick a free time slot of the required conference room and book the meeting indicating the
day, start time, end time and participants for the meeting. The system should validate that the
conference room is actually free (somebody else might have booked it during the time period of
creating the booking) and an e-mail message will be received by the meeting organizer, secretary
or whoever is using the system for the booking to indicate whether the booking is accepted or
rejected by the conference room. If successful, individual e-mail messages to each participant will
be sent inviting him/her to the meeting indicating the date, time and venue for the meeting. Their
calendars (inclusive of conference room) need to be automatically updated with the details of the
meeting. Booking details need to be maintained for each booking to indicate the date of booking,
start time and end time. Details of the participants are also stored in the system which will be
needed to manage the responses they send to the invitation as described below.

Upon receiving a meeting invitation, each executive can respond to it in different ways. They can
‘Accept’ the meeting request if they are okay with the time date etc. If they are not sure whether
they can participate in the meeting the response should be ‘Tentative’. If they are unable to
participate then the response would be ‘Declined’. The meeting organizer needs to be informed of
the response of each participant via e-mail. Summary of the responses can be viewed by the
meeting organizer or the secretary at any time. Depending on the responses, the meeting organizer
can proceed with, cancel or re-schedule the meeting.

If a meeting is cancelled, all participants are informed by email about the cancellation and their
calendars need to be automatically updated indicating the booked time as free. The conference
room’s calendar should also get updated. It should be noted that a meeting can only be cancelled
by the meeting organizer (person who has scheduled the meeting) or the secretary. All the booking
details and participant information should also get detect if the meeting is cancelled.

If a meeting is re-scheduled then the availability of the conference room is validated as before and
each participant is informed about the change. They need to respond as described above.
Sometimes it is necessary to schedule recurring meetings. For example there can be a meeting
scheduled to discuss the status of a certain project every Monday at 9.00 AM for one hour for a
designated period of time. The system should be able to cater to this need too. When such a meeting
is scheduled, one booking is created with multiple booking details for each meeting date until the
end date. The conference room and all participants’ calendars should get updated until the end
date. The secretary also can schedule meetings for an executive if he/she is given the required
details.

A Mobile Application also would be needed to support the Bookings for executives, view
calendars, cancellation of meetings etc. Cancellation of bookings can be done only by the executive
who has reserved the room. Executives should have an option in the mobile application to send
the details to the secretary if the booking is needed. If the booking is successful an SMS with the
details to the secretary if the booking is needed. If the booking is successful an SMS with the
details will be send to the executive who reserved the room. The mobile application will not be
available to the secretary.

The system should remind all participants about the meeting 15 minutes before the scheduled start
time by sending a SMS. This has to be done for all the bookings including mobile bookings.

Imagine that you have been assigned as a system Analyst by the e-Builders Systems Development
PLC to prepare a fully descriptive documentation comprised of Time Management System
analysis & designing information. In order to begin with user requirement gathering & system
environment analysis you are free to choose any organization to conduct interviews & site
observations. In prior commencing with system investigation activities proper approval should be
given to you by authorized officials of companies that you are visiting. In order to get the approval
you can forward ICBT Campus official request letter to them.

Tasks
1. Conduct an organizational analysis and report the findings of the organization/ institution
to what the information system will be implemented. Further justify suitability of the
information system for the same according to the present situation. (20 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. (20
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. (20 Marks)
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. (20 Marks)
5. Provide a comprehensive conclusion about the system by considering requirements and
specification of the information system tangible and intangible benefits expected. The
explanation should be further supported by scalability of the system based on future
requirements.(20 Marks)
General Guidelines for Students

1. With knowledge gain from the case study/Real world Scenario, analyse the facts carefully
and try to understand the association between each entity in the environment. Also identify
the data that is, needed to be stored for each entity and its relationships. Any applicable
assumptions made, should be clearly mention with proper justification.
2. Final report should be in professional manner and with proper formatting.
3. The student needs to give priority in designing the software product of the information
system.
4. Organizational visits & information gathering can be done in both individual and group
basis which not exceeding 4 members per group.
5. Before organizational / Work site visits students are expected to obtain ICBT official letter
requesting the relevant company for conducting information gathering work within their
premises.
6. Please note that students are expected to maintain backup copies of work in different media.
Due to any hardware, software malfunctions or virus attacks, assignment deadline will not
be lifted.

Submission Guidelines

Report Structure:

 Executive Summery
 Table of contents ,Table of Figures, Table of Tables
 Introduction of the Organization & its operational environment
 Explanation of current System & Drawbacks
 New System / Modified System Explanation
 New System Design (Diagrams, Algorithms, Decision Trees, Decision Tables, System
development Life cycle etc.)
 Conclusion
 Future Recommendation
 Gantt chart & its Description
 Referencing
 Appendix (Appendix A, Appendix B, etc.) for Group meetings, Samples of Questionnaire
Report Format:

 Submission format Report


 Paper Size: A4
 Words: 3000 words
 Printing Margins: LHS; RHS: 1 Inch
 Binding Margin: ½ Inch
 Header and Footer: 1 Inch
 Basic Font Size: 12
 Line Spacing: 1.5
 Font Style: Times New Roman
 Referencing should be done strictly using Harvard system
Assessment Criteria

Task (1) contains 20 marks.

Marks Marks
Criteria obtained
by the
Out of student
20 for the
answer
provided
Fail

 Provide clear idea about the organization to


which the information system is proposed 0-8
based on vision, mission, objectives, and
goals of the organization.

Pass
 Provide clear idea about the organization to
which the information system is proposed
based on vision, mission, objectives, and
8-12
goals of the organization.
 Management hierarchy of the organization is
included

Good

 Provide clear idea about the organization to


which the information system is proposed
based on vision, mission, objectives, and
goals of the organization.
 Management hierarchy of the organization is
included

 Description of the selected one of current


12-14
systems & its nature of operation
(Computerized/ manual/ Semi Computerized)
have been done that belongs to a specific
department/functional process of the
organization.

 Explanation has been done based on main


objectives expected by the organization from
the selected current system.
Excellent
 Provide clear idea about the organization to
which the information system is proposed
based on vision, mission, objectives, and
goals of the organization.
 Management hierarchy of the organization is
included

 Description of the selected one of current


systems & its nature of operation
(Computerized/ manual/ Semi Computerized)
have been done that belongs to a specific
department/functional process of the
organization.

 Explanation has been done based on main 14-20


objectives expected by the organization from
the selected current system.

 Justification has been done based on the purpose &


relevancy of the tool/s selected for gathering
information.
 Samples of the Questionnaire & Interviews attached.
 The sample questioner contains open type & close
type questions in order to specifically gather
information relevant to current system.
 At least economic, technical, operational, legal
feasibility study explained based on proposing system
 Proper justifications have provided for system
adaptation based on feasibility study.
Task (2) contains 20 marks.

Marks Marks
Criteria obtained
by the
Out of student
20 for the
answer
provided
Fail

 System Development life cycle explained


such as Communication, planning, Designing,
0-8
Development & Testing, Implementation but
no mapping has been done with system
implemented.

Pass
 At least Five stages of the System
Development life cycle explained such as
Communication, planning, Designing, 8-12
Development & Testing, Implementation.
 Every stage has been mapped with proposing
system development & designing activities.
Good
 At least Five stages of the System
Development life cycle explained such as
Communication, planning, Designing,
Development & Testing, Implementation.
 Every stage has been mapped with proposing 12-14
system development & designing activities.
 The description based on Prescriptive,
Incremental, Evolutionary, Agile &
Specialized Process Models

Excellent

 At least Five stages of the System


Development life cycle explained such as
Communication, planning, Designing,
Development & Testing, Implementation.

 Every stage has been mapped with proposing


system development & designing activities.
 The description based on
Prescriptive,Incremental,Evolutionary,Agile 14-20
& Specialized Process Models
 Justifications have been done based on the
qualities of the proposing system.

Task (3) contains 20 marks.

Marks Marks obtained


Criteria by the student
Out of 20 for the answer
provided
Fail
 Use ER diagrams to design data model of the
0-8
proposing system but some errors exists.

Pass
 Use ER diagrams to design data model of the
proposing system.

 Find entities, Attributes, relationships, Primary


keys, , different cardinalities, , composite keys,
8-12
and other entities.

 Attributes, Entities, Relationships & Cardinalities


properly selected & illustrated.

 Write a data dictionary for the ER diagram.


Good

 Use ER diagrams to design data model of the


proposing system.

 Find entities, Attributes, relationships, Primary


12-14
keys, proper relationships with cardinality ratios.

 Attributes, Entities, Relationships & Cardinalities


properly selected & illustrated.

 Write a data dictionary for the ER diagram.


Excellent

 Use ER diagrams to design data model of the


proposing system.

 Find entities, Attributes, relationships, Primary


keys, proper relationships with cardinality ratios.

 Attributes, Entities, Relationships & Cardinalities 14-20


properly selected & illustrated.

 Write a data dictionary for the ER diagram.

 Has been used standard format for the Data


dictionary.

Task (4) contains 20 marks.

Marks Marks obtained


Criteria by the student
Out of 20 for the answer
provided
Fail

 Draw context level Data Flow Diagram to


illustrate functional model of the proposing 0-8
system with some errors.

Pass
 Draw context level Data Flow Diagram to
illustrate functional model of the proposing
system.
 External Entitles, Main Information System &
Information Initial flow between External 8-12
Entities & Main Information System have been
identified & illustrated.

 Proper Process & data flow labeling used

Good
 Draw context level Data Flow Diagram to
12-14
illustrate functional model of the proposing
system.
 External Entitles, Main Information System &
Information Initial flow between External
Entities & Main Information System have been
identified & illustrated.

 Draw Level 0 Data Flow Diagram to illustrate


functional model of the proposing system.
showing at least five different transaction
processors

 External Entities, Major Processes, Data Storages


& initial Data Flows & Intermediate Data Flows
in between them have been Identified &
illustrated.

 Draw a Level 1 Data Flow Diagram to illustrate


functional model of the proposing system
considering detailed analysis.
 External Entities, Sub Processes, Data Storages &
initial Data Flows & Intermediate Data Flows in
between them have been Identified & illustrated.

 Proper Process & data flow labeling used

Excellent

 Draw context level Data Flow Diagram to illustrate


functional model of the proposing system.

 External Entitles, Main Information System &


Information Initial flow between External Entities &
Main Information System have been identified &
illustrated.
14-20
 In order to further explain internal logic of the major
processes’ of the information system, Structured
English, Decision Trees & Decision Tables properly
used for DFD level 0 processes.
 Process specifications have been included using
standard process specification format
 Object type, Data Type, Data Inflow & Data Out
Flow have been described.
 Write a data dictionary for the DFD level 0 using
standard format.
 Top down designing technique & the bottom up
designing technique should be properly explained
considering the functional design.
 UML diagrams (USE-CASE and CLASS) should be
tally with system’s functionalities.

Task (5) contains 20 marks.


Marks Marks obtained
Criteria by the student
Out of 20 for the answer
provided
Fail
 Poor conclusion has been provided without based on
system’s functionalities. 0-8

Pass
 Conclusion should be given based on the
proposing information system’s functionalities & 8-12
those benefits for the organization’s goals to
achieve.
Good
 Conclusion should be given based on the
proposing information system’s functionalities &
those benefits for the organization’s goals to
achieve.

 Explanation has been given by incorporating


12-14
BSO(Business System Options) and TSO
(Technical System Options) .

 Clearly explain how does business system options


supported by technical system options

Excellent

 Explanation has been given by incorporating


BSO(Business System Options) and TSO
14-20
(Technical System Options) .

 Clearly explain how does business system options


supported by technical system options.
 Conclusion should be given based on the
proposing information system’s functionalities &
those benefits for the organization’s goals to
achieve.

 Future recommendations should be given based


on the possible enhancements of the proposing
information system.