Scribd
Upload
29 views

SAD Assignment 4

The document proposes developing a college note system using an agile methodology. It describes the current manual note-taking process and potential improvements like automated OCR, searchable notes, and mobile access. The agile method is chosen for its ability to adapt to changing requirements, provide frequent feedback, and incrementally develop and quickly release new features. The system would have organizational boundaries for admins, students, and teachers, and functional boundaries for content management, user accounts, and more.

Uploaded by

Nyi Htwe
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
29 views

SAD Assignment 4

The document proposes developing a college note system using an agile methodology. It describes the current manual note-taking process and potential improvements like automated OCR, searchable notes, and mobile access. The agile method is chosen for its ability to adapt to changing requirements, provide frequent feedback, and incrementally develop and quickly release new features. The system would have organizational boundaries for admins, students, and teachers, and functional boundaries for content management, user accounts, and more.

Uploaded by

Nyi Htwe
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 5

Project Identification and Selection

Group-1
(College Note System)

Current Situation:

Listing of manual and automated processes:


● Students have to take handwritten or printed notes and physically share them with
classmates.
● Students take notes in their mobile phone or personal computer and store them locally.
● Only able to share emails with others.
● Teachers have to distribute some lecture notes or slides via printouts or email
attachments.
Listing of manual and automated data
● Manual Data
● Handwritten notes
● Printed notes distributed by teacher.
● Automated Data
● Document file using Microsoft word.
● Document file in PDF data
● PowerPoint slides
Technology inventory
➢ Simple computer for emailing and writing document files to send email.
Human resource inventory
❖ Teacher: Write notes and distribute to students after class
❖ Student: Take notes of the class and share printed notes from the teacher.

Potential Future Improvements:

Listing of manual and automated processes:


● Manual process:
○ Able to share with a click of a button.
○ Teachers can comment on student notes before approval.
○ Teachers and students upload recorded lectures links and sync with notes.
○ Chat/discussion forums for students to discuss notes and collaborate.

● Automated process:
○ Automated optical character recognition (OCR) when students upload
handwritten/scanned notes. This makes the notes searchable.
○ Allow searching/filtering of notes by class, topic, keyword etc.
○ Able to share multiple files and file types.
○ Mobile app to allow access and notifications on phones/tablets.

Listing of manual and automated data


● Manual data
● Handwritten notes
● Automated data
● All data will be stored in the database.
Technology inventory
➢ Hosting service for college note system since it will be via web system.
Human resource inventory
❖ Teacher: upload notes and approve notes via web system respectively by each department
❖ Student: upload notes after class respectively by each department
❖ System admin: maintain system.
System Development Methodologies
For our student notes project, we have decided to choose the Agile system development
method to bring the best for our system. We believed that this method is the most suitable and
convenient in development process because agile development offers flexibility both in system
development and planning since our system could have discovered more features during the
development process. And here are the reasons for why we decided to use the Agile method:

 Adaptability to Changing Requirements: Agile provides flexibility to accommodate


evolving needs in educational settings, allowing seamless integration of new features as
they are identified during development.
 Frequent Feedback Loops: Agile ensures regular feedback from teachers and
students, enabling real-time refinement of the system. Continuous reviews and iterations
improve overall satisfaction and align the final product with user expectations.
 Incremental Development and Quick Releases: Agile method’s incremental approach
allows for swift delivery of functional components. In an educational context, this means
quicker access to new features, early testing, and validation, enhancing the overall
effectiveness of the note-sharing system.
 Enhanced Collaboration and Communication: Agile fosters collaboration among
team members, stakeholders, teachers, and students. Open communication channels
and collaborative decision-making ensure a responsive, user-friendly system that aligns
closely with the evolving needs of the dynamic academic environment in a Students
Note project.
 Mitigation of Risks Through Iterative Testing: Agile method’s iterative development
model allows for continuous testing and validation of features, reducing the likelihood of
major errors going unnoticed until the end of the project. This proactive approach to
testing ensures a more reliable and robust student note-sharing system.
 Optimized Resource Utilization: Agile maximizes resource efficiency by prioritizing the
most valuable features early in the development process. This ensures that essential
functionalities are addressed first, providing tangible benefits to users while allowing for
adjustments based on ongoing feedback. This optimized resource allocation contributes
to the overall success of the Students Note project.
Organizational Boundaries
 Admins
 Students
 Teachers

Process Boundaries
 Content Management
 User Account Management
 Search or Filtering Contents
 Discussion Forums
 Commenting
 Self-User Onboarding
 Admin Management
 Displaying Contents

Functional Boundaries
 Content Management
 Upload
 Delete
 Update
 Approve
 Reject
 Unpublish
 Publish
 Archive
 Admin Management
 Login/Logout
 Create New User
 User Permission Authorization
 User Account Suspension
 Account Deactivation
 User Account Deactivation

 User Accounts Management
 Login
 Logout
 Account Deactivation

 Contents Approval
 Content Rejection

You might also like