You are on page 1of 73

Assignment Brief

Assignment front sheet

Qualification Unit number and title

Pearson BTEC Level 5 HND Diploma in Computing and Systems


Unit 42 H/601/1537/ Programming in .Net
Development

Student Name BTEC Number Assessor name

Date issued Completion date Submitted on

Assignment title Programming solution for Problem

In this assessment you will have the In this assessment you will have the A/NA
A/N opportunity to present evidence that shows
AC opportunity to present evidence that shows
A AC you are able to:
you are able to:

4.3 evaluate independent feedback on a developed


discuss the principles, characteristics and
1.1 Java program solution and make
features of programming in Java
recommendations for improvements

critically evaluate the environmental 4.4 create user documentation for the developed
1.2
flexibility of programming in Java Java program solution

design a Java programming solution to a 4.5 create technical documentation for the support
2.1
given problem and maintenance of a Java program solution.

explain the components and data and file M1 Identify and apply strategies to find appropriate
2.2 structures required to implement a given solutions
design

implement a Java programming solution M2 Select/design and apply appropriate


3.1
based on a prepared design methods/techniques

define relationships between objects to M3 Present and communicate appropriate findings


3.2
implement design requirements

implement object behaviors using control D1 Use critical reflection to evaluate own work and
3.3
structures to meet the design algorithms justify valid conclusions
identify and implement opportunities for error D2 Take responsibility for managing and organizing
3.4
handling and reporting activities

make effective use of an Integrated D3 Demonstrate convergent/lateral/ creative


3.5 Development Environment (IDE) including thinking
code and screen templates

4.1 critically review and test a Java programming


solution

4.2 analyze actual test results against expected


Grade
results to identify discrepancies

Learner declaration

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

Student signature: Date:


Preparation Guidelines of the Coursework Document

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 be sure to fill the details correctly.
2. This entire brief should be attached in first before you start answering.
3. All the assignments should prepare using word processing software.
4. All the assignments should print in A4 sized paper, and make sure to only use one side printing.
5. Allow 1” margin on each side of the paper. But on the left side you will need to leave room for binging.
6. Ensure that your assignment is stapled or secured together in a binder of some sort and attach the Softcopy (CD)
of your final document, system on last page.

Word Processing Rules

1. Use a font type that will make easy for your examiner to read. The font size should be 12 point, and should be in
the style of Time New Roman.
2. Use 1.5 line word-processing. Left justify all paragraphs.
3. Ensure that all headings are consistent in terms of size and font style.
4. Use footer function on the word processor to insert Your Name, Subject 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 edit your assignment.
6. Ensure that your printer’s output is of a good quality and that you have enough ink to print your entire
assignment.

Important Points:

1. Check carefully the hand in date and the instructions given with the assignment. Late submissions will not be
accepted.
2. Ensure that you give yourself enough time to complete the assignment by the due date.
3. Don’t leave things such as printing to the last minute – excuses of this nature will not be accepted for failure to
hand in the work on time.
4. You must take responsibility for managing your own time effectively.
5. 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.
6. Failure to achieve at least a PASS grade will result in a REFERRAL grade being given.
7. Non-submission of work without valid reasons will lead to an automatic REFERRAL. You will then be asked to
complete the assignment with the next batch.
8. Take great care that if you use other people’s work or ideas in your assignment, you properly reference them,
using the HARVARD referencing system, in you text and any bibliography, otherwise you may be guilty of
plagiarism.
9. If you are caught plagiarising you could have your grade reduced to A REFERRAL or at worst you could be
excluded from the course.
Assignment brief

Unit number and title Unit 42 Programming in .Net

Qualification Pearson BTEC HND Diploma in Computing and Systems Development

Start date
Deadline/hand-in

Assessor

Assignment title Programming solution for a scenario

Purpose of this assignment

To provide learners with an understanding of the principles of programming using a .NET framework as an underpinning
technological concept in the fields of programming and systems development.

Scenario

“Southend School” is a leading private sector education institute. The school decided to create a windows
application to keep track on student assignment submission who follows HND. There are number of batches
with different number of students follow 17 subjects. There are three main users in the system and their
functionalities are as follows

Student Coordinator

1. Insert student information and allocating them in to different batches


2. Update student information
3. Accepting student assignment and change the status in the system as “submitted”
4. Insert /update the assignment grades
5. View the assignment submission status based on the student/ batch/ subject

Student

6. View their information


7. View their assignment status (submitted/ not Submitted)
8. View their assignment grades
Administrator

9. Creating users: Creating new users, managing and modify the existing users

Students are free to make necessary assumption on system design & granting access permissions other than
mentioned within the scenario, but all suggestions must be well explained with the valid reasons.

Task 1

You are required to prepare a PowerPoint presentation about the .Net framework. You need to include below
points in your presentation.

1. Discuss principles, characteristics and features of programming using .Net framework. (LO
1.1)
2. Critically compare different types of .Net framework architectures. (LO1.2)
3. Critically evaluate the components that support .NET framework for your design solution.
(LO 1.3)

Task 2

Create a suitable Use Case diagram, a class diagram and sequence diagram to address the above given
scenario. You are free to make any valid assumptions, but make sure to mention those in your report (LO
2.1,M1.1)

Task 3

I. Propose a suitable database design with a normalized schema for the above solution. (LO
2.2,M2.1)
II. Comment on the GUI components you used in designing the above solution.
(LO 2.2)

Task 4 Identify, how you suppose to deploy the designed solution. Provide methodical instructions on, how
the application deployment should occur (LO 2.3)

Task 5 Base on the design, Implement a .NET programming solution (LO 3.1). Provide appropriate
conclusion including program strengths, weaknesses and enhancement that can be accomplished with the
given solution (D1.1)
Task 6. Analyze the events and control structures you identify in implementing the proposed design with
valid examples, taken from the system. (LO 3.2)

Task 7 Error handling is one of the major factor in determining the success of a software solution. Identify
and implement opportunities to apply the error handling in developed solution. (LO 3.3)

Task 9 Specify how much supportive the .Net IDE in creating a programmatic solution for the given scenario.
Support your answer with appropriate illustrations. (LO 3.4)

Task 11. For the developed program application; produce a test plan with appropriate test cases to
carry out the testing process and critically analyse your test results.
(LO 4.1, LO 4.2)

Task 12. Provide the implemented system to someone else (may be your friend) get their feed about your
system. You have to include copies of questionnaires you provided to them as evidences. Write a small report
on how you plan to improve your system further more based on the findings you made. (LO 4.3)

Task 13. Create a user document (User manual) for the developed solution to assist the users to work with it.
Brief explanation and screen capturing would be helpful in this section (LO 4.4,M3.1).
Task 14. Provide a suitable technical documentation which covers designs, platform, file structures, and
instructions for maintenance (LO4.5, M3.1)

Task 17: Assignment Gantt chart should be realistic and reflect the management of the activities.
Furthermore, the challenges faced when trying to achieve the milestone need to be explained. (D2.3)

Task 18: Appropriate security features, such as login screens and role based security can be incorporated and
openness to new ideas to indicate the creative and innovative thinking of the student. (D3.5)
Supportive Sources

Books

Esposito D – Programming Microsoft ASP.NET MVC (Microsoft, 2010) ISBN-10: 0735627142


Libert J, Horovitz A – Programming .NET 3.5 (O’Reilly, 2008) ISBN-10: 059652756X
Lowy J – Programming .NET Components: Design and Build .NET Applications Using Component-
Oriented Programming (O’Reilly, 2005) ISBN-10: 0596102070

Websites

http://msdn.microsoft.com/en-gb/library/zw4w595w.aspx
www.dotnet-guide.com/
www.programmingtutorials.com/vbnet.aspx
Achievement Summary

Learning Outcomes Summary of Evidence required by the student Achieved Feedback

LO1 Understand the principles of programming using a .NET framework

LO1.1 discuss the principles, Identify and explain the different characteristics and features
characteristics and features of of the .Net framework
programming using a .NET
framework

LO1. 2. critically compare Written Report: Conduct a critical analysis on different


different types of .NET framework types of .NET frameworks
architectures

LO1.3 critically evaluate the Written Report: Analytically assess the components that
components that support the support .NET framework for your design solution
.NET framework

LO2 Be able to design .NET solutions

LO 2.1 design a .NET Written report: Provide Use Case diagram, class diagram
programming solution to a given and sequence diagram for the proposed solution
problem
LO 2.2 explain the components Written Report: Propose a suitable database design and
and data and file structures normalized schema for the proposed solution
required to implement a given
design

LO2.3 evaluate potential delivery Written report: Create a deploy file for the designed
environments and solution with the instruction
interaction

LO3 Be able to implement .NET solutions

LO 3. 1. implement a .NET Practical observation and written report: Implement a


programming solution based on a .NET programming solution based on the design
prepared design

LO 3. 2 implement event handling Practical observation and written report: Implement event
using control structures to handling with appropriate messages
meet the design algorithms

LO3.3 identify and implement Practical observation and written report: Identify syntax
opportunities for error and logical errors. Identify the error handling techniques for
handling and reporting
the developed solution

LO 3.4 make effective use of an Practical observation and written report: identify the
Integrated Development effective ways of using an Integrated Development Environment
Environment (IDE) including code (IDE) for you design
and screen
templates
LO4 Be able to test and document .NET solutions.

LO4.1. LO 4.1: Critically review Written Report: Provide a test plan with appropriate test
and test a .NET programming cases to carry out the testing process
solution

LO4.2. LO 4.2: Analyze actual Written Report: Critically analyse the test results against
test results against expected results expected results
to identify discrepancies

LO4.3 Evaluate independent Written Report:


feedback on a developed .NET
program solution and make Attach user feedbacks. Analysis and evaluate given feedbacks.
recommendations for
improvements

LO 4.4 Create user documentation Written Report: Use proper format to prepare a user manual
for the developed .NET program
solution

LO 4.5 Create technical Written Report: Provide a suitable technical documentation


documentation for the support and
maintenance of a .NET program
solution.
In addition to the above PASS criteria, this assignment gives you the opportunity to submit evidence in order to achieve the following MERIT and
DISTINCTION grades

Feedback
Grade Descriptor Indicative characteristic/s Contextualisation

M1 Identify and apply strategies to M1.1 Effective judgments have Strong justifications and explanation have
find appropriate solutions been made been made in relation to the proper usage
of the UML diagrams

M2 Select/design and apply M2.1 Relevant theories and Apply theories with correct techniques
appropriate methods/techniques techniques have been used. when designing the DB

M3 Present and communicate M3.1 The appropriate Structure and Documentation is well structured adhering
appropriate findings approach has been used to the formatting guidelines with non-
overlapping facts. Data provided are
accurate, reliable and consistent. Maintain
good academic writing throughout the
report and use of language syntax (different
sections of the source codes can be print).

D1 Use critical reflection to evaluate D1.1 conclusions have been arrived Proper conclusions, future
own work and justify valid at through synthesis of ideas and recommendations, and critically analyze
conclusions have been justified your own work

D2 Take responsibility for managing D2.3 Activities have been managed.


and organising activities Gantt chart must be provided in the
appendix section for the report explaining
how the activities have undertaken and
time was managed

D3 Demonstrate convergent/lateral/ D3.5 innovation and creative Incorporate creative ideologies for the
creative thinking thought have been applied propose system (Eg: Appropriate security
features, such as login screens and role
based security )
Assignment Feedback

Formative Feedback: Assessor to Student


Summative feedback

Improvements
Assessor Signature Date

IV Signature Date
Acknowledgement
Table of contents

Task 1 ........................................................................................................................................ 20

You are required to prepare a PowerPoint presentation about the .Net framework. You need to
include below points in your presentation................................................................................. 20

1. Discuss principles, characteristics and features of programming using .Net framework. . 20

2. Critically compare different types of .Net framework architectures. ................................ 20

3. Critically evaluate the components that support .NET framework for your design solution.
20

Task 2 ........................................................................................................................................ 26

Create a suitable Use Case diagram, a class diagram and sequence diagram to address the above
given scenario. You are free to make any valid assumptions, but make sure to mention those in
your report. ................................................................................................................................ 26

Use case Diagram .................................................................................................................. 26

Class Diagram........................................................................................................................ 30

Sequence diagram .................................................................................................................. 33

Task 3 ........................................................................................................................................ 37

I. Propose a suitable database design with a normalized schema for the above solution. .... 37

II. Comment on the GUI components you used in designing the above solution. ................. 38

Task 4 ........................................................................................................................................ 39

Identify, how you suppose to deploy the designed solution. Provide methodical instructions on,
how the application deployment should occur. ......................................................................... 39

Task 5 ........................................................................................................................................ 44

Base on the design, Implement a .NET programming solution. Provide appropriate conclusion
including program strengths, weaknesses and enhancement that can be accomplished with the
given solution. ........................................................................................................................... 44

Task 6. ....................................................................................................................................... 45
Analyze the events and control structures you identify in implementing the proposed design with
valid examples, taken from the system. .................................................................................... 45

Task 7 ........................................................................................................................................ 48

Error handling is one of the major factor in determining the success of a software solution.
Identify and implement opportunities to apply the error handling in developed solution. ....... 48

Task 8 ........................................................................................................................................ 51

Specify how much supportive the .Net IDE in creating a programmatic solution for the given scenario.
Support your answer with appropriate illustrations. ............................................................................... 51

Task 9. ..................................................................................................................................................... 53

For the developed program application; produce a test plan with appropriate test cases to carry out the
testing process and critically analyses your test results. ......................................................................... 53

Task 10. ................................................................................................................................................... 59

Provide the implemented system to someone else (may be your friend) get their feed about your system.
You have to include copies of questionnaires you provided to them as evidences. Write a small report on
how you plan to improve your system further more based on the findings you made. .......................... 59

Task 11. ................................................................................................................................................... 61

Create a user document (User manual) for the developed solution to assist the users to work with it.
Brief explanation and screen capturing would be helpful in this section................................................ 61

Task 12. Provide a suitable technical documentation which covers designs, platform, file structures, and
instructions for maintenance. .................................................................................................................. 67

Task 13:................................................................................................................................................... 69

Assignment Gantt chart should be realistic and reflect the management of the activities. Furthermore, the
challenges faced when trying to achieve the milestone need to be explained. ....................................... 69

Task 14: Appropriate security features, such as login screens and role-based security can be incorporated
and openness to new ideas to indicate the creative and innovative thinking of the student. .................. 71

Conclusion .............................................................................................................................................. 73
Table of Figures

Figure 1 ......................................................................................................................................... 20
Figure 2 ......................................................................................................................................... 21
Figure 3 ......................................................................................................................................... 21
Figure 4 ......................................................................................................................................... 22
Figure 5 ......................................................................................................................................... 22
Figure 6 ......................................................................................................................................... 23
Figure 7 ......................................................................................................................................... 23
Figure 8 ......................................................................................................................................... 24
Figure 9 ......................................................................................................................................... 24
Figure 10 ....................................................................................................................................... 25
Figure 11 ....................................................................................................................................... 29
Figure 12 ....................................................................................................................................... 32
Figure 13 ....................................................................................................................................... 36
Figure 14 ....................................................................................................................................... 37
Figure 15 ....................................................................................................................................... 61
Figure 16 ....................................................................................................................................... 62
Figure 17 ....................................................................................................................................... 62
Figure 18 ....................................................................................................................................... 63
Figure 19 ....................................................................................................................................... 63
Figure 20 ....................................................................................................................................... 64
Figure 21 ....................................................................................................................................... 64
Figure 22 ....................................................................................................................................... 65
Figure 23 ....................................................................................................................................... 66
Figure 24 ....................................................................................................................................... 68
Task 1

You are required to prepare a PowerPoint presentation about the .Net


framework. You need to include below points in your presentation.

1. Discuss principles, characteristics and features of programming using


.Net framework.

2. Critically compare different types of .Net framework architectures.

3. Critically evaluate the components that support .NET framework for


your design solution.

Figure 1
Figure 2

Figure 3
Figure 4

Figure 5
Figure 6

Figure 7
Figure 8

Figure 9
Figure 10
Task 2

Create a suitable Use Case diagram, a class diagram and sequence diagram to
address the above given scenario. You are free to make any valid assumptions,
but make sure to mention those in your report.

Use case Diagram


The use case diagram is a behavioral UML diagram type and frequently used to analyze various
systems. They enable you to visualize the different types of roles in a system and how those roles
interact with the system.

Importance of Use Case Diagrams

As mentioned before use case diagrams are used to gather a usage requirement of a system.
Depending on your requirement you can use that data in different ways. Below are few ways to
use them. To identify functions and how roles interact with them -The primary purpose of use case
diagrams.

For a high-level view of the system-Especially useful when presenting to Administrator or


stakeholders. You can highlight the roles that interact with the system and the functionality
provided by the system without going deep into inner workings of the system.

To identify internal and external factors -This might sound simple but in large complex projects a
system can be identified as an external role in another use case.

Use Case Diagram objects

Use case diagrams consist of 4 objects.

1. Actor
2. Use case
3. System
4. Package
Actor

Actor in a use case diagram is any entity that performs a role in one given system. This could be a
person, organization or an external system and usually drawn like skeleton shown below.

Use Case

A use case represents a function or an action within the system. It’s drawn as an oval and named
with the function.

System

The system is used to define the scope of the use case and drawn as a rectangle. This an optional
element but useful when you’re visualizing large systems. For example, you can create all the use
cases and then use the system object to define the scope covered by your project. Or you can even
use it to show the different areas covered in different releases.

Package

The package is another optional element that is extremely useful in complex diagrams. Similar to
class diagrams, packages are used to group together use cases. They are drawn like the image
shown below.

Relationships in Use Case Diagrams

There are some types of relationships in a use case diagram. They are

Association between an actor and a use case

Generalization of an actor

Extend relationship between two use cases

Include relationship between two use cases


How to Create a Use Case Diagram

1. Identifying Actors
Actors are external entities that interact with your system. It can be a person, another system or an
organization.

2. Identifying Use Cases


Now it’s time to identify the use cases. A good way to do this is to identify what the actors need
from the system.

Top level use cases should always provide a complete function required by an actor. You can
extend or include use cases depending on the complexity of the system. Once you identify the
actors and the top level use case you have a basic idea of the system. Now you can fine tune it and
add extra layers of detail to it.

3. Look for Common Functionality to use Include


Look for common functionality that can be reused across the system. If you find two or more use
cases that share common functionality you can extract the common functions and add it to a
separate use case. Then you can connect it via the include relationship to show that it’s always
called when the original use case is executed.

4. Optional Functions or Additional Functions


There are some functions that are triggered optionally. In such cases, you can use the extend
relationship and attach an extension rule to it.Extend doesn’t always mean it’s optional. Sometimes
the use case connected by extending can supplement the base use case.
Use case diagram for this system

Figure 11
Class Diagram

Class diagrams are one of the most useful types of diagrams in UML as they clearly map out the
structure of a particular system by modeling its classes, attributes, operations, and relationships
between objects. With our UML diagramming software, creating these diagrams is not as
overwhelming as it might appear.

Basic components of a class diagram

The standard class diagram is composed of three sections:

• Upper section: Contains the name of the class. This section is always required, whether
you are talking about the classifier or an object.
• Middle section: Contains the attributes of the class. Use this section to describe the qualities
of the class. This is only required when describing a specific instance of a class.
• Bottom section: Includes class operations (methods). Displayed in list format, each
operation takes up its own line. The operations describe how a class interacts with data.

Member access modifiers

All classes have different access levels depending on the access modifier (visibility). Here are the
access levels with their corresponding symbols:

• Public (+)
• Private (-)
• Protected (#)
• Package (~)
• Derived (/)
• Static (underlined)

Member scopes

There are two scopes for members: classifiers and instances.

Classifiers are static members while instances are the specific instances of the class. If you are
familiar with basic OO theory, this isn't anything groundbreaking.
Additional class diagram components

Classes: A template for creating objects and implementing behavior in a system. In UML, a class
represents an object or a set of objects that share a common structure and behavior. They're
represented by a rectangle that includes rows of the class name, its attributes, and its operations.
When you draw a class in a class diagram, you're only required to fill out the top row—the others
are optional if you'd like to provide more detail.

Name: The first row in a class shape.

Attributes: The second row in a class shape. Each attribute of the class is displayed on a separate
line.

Methods: The third row in a class shape. Also known as operations, methods are displayed in list
format with each operation on its own line.

Signals: Symbols that represent one-way, asynchronous communications between active objects.

Data types: Classifiers that define data values. Data types can model both primitive types and
enumerations.

Packages: Shapes designed to organize related classifiers in a diagram. They are symbolized with
a large tabbed rectangle shape.

Interfaces: A collection of operation signatures and/or attribute definitions that define a cohesive
set of behaviors. Interfaces are similar to classes, except that a class can have an instance of its
type, and an interface must have at least one class to implement it.

Enumerations: Representations of user-defined data types. An enumeration includes groups of


identifiers that represent values of the enumeration.

Objects: Instances of a class or classes. Objects can be added to a class diagram to represent either
concrete or prototypical instances.

Artifacts: Model elements that represent the concrete entities in a software system, such as
documents, databases, executable files, software components.
Inheritance: The process of a child or sub-class taking on the functionality of a parent or superclass,
also known as generalization. It's symbolized with a straight connected line with a closed
arrowhead pointing towards the superclass.

Class diagram for this system

Figure 12
Sequence diagram

UML Sequence Diagrams are interaction diagrams that detail how operations are carried out. They
capture the interaction between objects in the context of a collaboration. Sequence Diagrams are
time focus and they show the order of the interaction visually by using the vertical axis of the
diagram to represent time what messages are sent and when.

Sequence Diagrams captures:

• Interaction that takes place in a collaboration that either realizes a use case or an operation
(instance diagrams or generic diagrams)
• High-level interactions between user of the system and the system, between the system and
other systems, or between subsystems (sometimes known as system sequence diagrams)
Purpose of Sequence Diagram

• Model high-level interaction between active objects in a system


• Model the interaction between object instances within a collaboration that realizes a use
case
• Model the interaction between objects within a collaboration that realizes an operation
• Either model generic interactions (showing all possible paths through the interaction) or
specific instances of interaction (showing just one path through the interaction)

Sequence Diagrams at a Glance

Sequence Diagrams show elements as they interact over time and they are organized according to
object (horizontally) and time (vertically):

Object Dimension: The horizontal axis shows the elements that are involved in the interaction
conventionally, the objects involved in the operation are listed from left to right according to when
they take part in the message sequence. However, the elements on the horizontal axis may appear
in any order

Time Dimension: The vertical axis represents time proceedings (or progressing) down the page.
Sequence Diagram Notation

Actor

A type of role played by an entity that interacts with the subject (e.g., by exchanging signals and
data).External to the subject (i.e., in the sense that an instance of an actor is not a part of the instance
of its corresponding subject).Represent roles played by human users, external hardware, or other
subjects. An actor does not necessarily represent a specific physical entity but merely a particular
role of some entity person may play the role of several different actors and, conversely, a given
actor may be played by multiple different person.

Lifeline

A lifeline represents an individual participant in the Interaction.

Activations

A thin rectangle on a lifeline) represents the period during which an element is performing an
operation. The top and the bottom of the of the rectangle are aligned with the initiation and the
completion time respectively

Call Message

A message defines a particular communication between Lifelines of an Interaction. Call message


is a kind of message that represents an invocation of operation of target lifeline.

Return Message

A message defines a particular communication between Lifelines of an Interaction. Return


message is a kind of message that represents the pass of information back to the caller of a
corresponded former message.

Self-Message

A message defines a particular communication between Lifelines of an Interaction. Self-message


is a kind of message that represents the invocation of message of the same lifeline.
Recursive Message

A message defines a particular communication between Lifelines of an Interaction. Recursive


message is a kind of message that represents the invocation of message of the same lifeline. Its
target points to an activation on top of the activation where the message was invoked from.

Create Message

A message defines a particular communication between Lifelines of an Interaction. Create message


is a kind of message that represents the instantiation of (target) lifeline.

Destroy Message

A message defines a particular communication between Lifelines of an Interaction. Destroy


message is a kind of message that represents the request of destroying the lifecycle of target
lifeline.

Duration Message

A message defines a particular communication between Lifelines of an Interaction. Duration


message shows the distance between two time instants for a message invocation.

Note

A note (comment) gives the ability to attach various remarks to elements. A comment carries no
semantic force, but may contain information that is useful to a modeler.
Sequence diagram for this system

Figure 13
Task 3

I. Propose a suitable database design with a normalized schema for the


above solution.

Database design is the organization of data according to a database model. The designer determines
what data must be stored and how the data elements interrelate. With this information, they can
begin to fit the data to the database model. Database management system manages the data
accordingly.

Figure 14
II. Comment on the GUI components you used in designing the above
solution.

GUI Component

Components are elementary GUI entities, such as Button, Label, and Text Field. The main
functions of the system below that listed, they are using these Components to the Proper function.

• Login to System
• Add, delete and update students.
• Add, delete and update courses.
• Add, delete and update assignments.
• Registration courses for students.
• Uploading Ant/Nant script files.
• Running the Ant/Nant script files for testing the assignments.
• Generate Report for students.

Above functions are using with the button component, textbox, Drop down menu.
Task 4

Identify, how you suppose to deploy the designed solution. Provide methodical
instructions on, how the application deployment should occur.

Realizing the Database Design

Implementation involves the construction of a database according to the specification of a logical


schema. This will include the specification of an appropriate storage schema, security enforcement,
and external schema and so on. Implementation is heavily influenced by the choice of available
DBMSs, database tools and operating environment. There are additional tasks beyond simply
creating a database schema and implementing the constraints – data must be entered into the tables,
issues relating to the users and user processes need to be addressed, and the management activities
associated with wider aspects of corporate data management need to be supported. In keeping with
the DBMS approach, we want as many of these concerns as possible to be addressed within the
DBMS. We look at some of these concerns briefly now.

In practice, implementation of the logical schema in each DBMS requires a very detailed
knowledge of the specific features and facilities that the DBMS has to offer. In an ideal world, and
in keeping with good software engineering practice, the first stage of implementation would
involve matching the design requirements with the best available implementing tools and then
using those tools for the implementation. In database terms, this might involve choosing vendor
products with DBMS and SQL variants most suited to the database we need to implement.
However, we don’t live in an ideal world and often, hardware choice and decisions regarding the
DBMS will have been made well in advance of consideration of the database design.
Consequently, implementation can involve additional flexing of the design to overcome any
software or hardware limitations.
Realizing the GUI Design

After the logical design has been created, we need our database to be created according to the
definitions we have produced. For an implementation with a relational DBMS, this will probably
involve the use of SQL to create tables and constraints that satisfy the logical schema description
and the choice of appropriate storage schema (if the DBMS permits that level of control).

One way to achieve this is to write the appropriate SQL DDL statements into a file that can be
executed by a DBMS so that there is an independent record, a text file, of the SQL statements
defining the database. Another method is to work interactively using a database tool like SQL
Server Management Studio or Microsoft Access. Whatever mechanism is used to implement the
logical schema, the result is that a database, with tables and constraints, is defined but will contain
no data for the user processes.

Field Name Data Null Key References Length Description


Type

name String No 50 Coordinator name

ID String No PK 50 Coordinator number

password String No 50 Coordinator password

Email String No 50 Coordinator email


Field Name Data Null Key References Length Description
Type

name String No 50 Student name

ID String No PK 50 Student number

password String No 50 Student password

Email String No 50 Student email

Field Name Data Null Key References Length Description


Type

name String No 50 Administrator name

ID String No PK 50 Administrator number

password String No 50 Administrator password

Email String No 50 Administrator email

Field Name Data Type Null Key References Length Description

name String No 50 Course name

number String No PK 50 Course number

credit Integer No 4 Course credit

type String No 50 Course type

level String No 50 Course level


Field Name Data Null Key References Length Description
Type

Number String No PK 50 Assignment number

Course Course number


Course Number String No PK 50
(number)
Description of the
Description String No 50
assignment
How to upload and
Instruction String No 50 download the assignment

StartTime Datetime No PK 8 Start time of the assignment

EndTime Datetime No PK 8 End time of the assignment

The benefits of this


Motivation String Yes 50
assignment
the allowed number of
TypeofWork Integer Yes 4 students in this
assignment
If it is possible to submit the
IsStrict Boolean No 2 assignment after the deadline

Uniform resource locator of


URL String Yes 50 the assignment

Field Name Data Null Key References Length Description


Type

Student (ID) Student number


StdID String No PK 50

Student Student name


StdName String No 50
(name)
Course Course number
CourseID String No 50
(number)
Course Course Name
CourseName String No 50
(name)
Course semester
Semester Integer No PK 4

Date Datetime No PK 8 Date of registration


Mark Integer Yes 4 Student Mark
Field Name Data Type Null Key References Length Description

StudentNumber String No PK Student (ID) 50 Student number


Course Course number
CourseNumber String No 50
(number)
Assignment Assignment
AssignmentNumber String No 50
(number) number
Start time of the
StartTime Datetime No PK 8
assignment
End time of the
EndTime Datetime No PK 8
assignment
SubmitDate Datetime Yes 8 Submit date
The number of
times of
count Integer Yes 4
uploading the
assignment
Accepted the
accepted Boolean Yes 2
assignment or not
Uniform resource
URL String Yes 50 locator of the
solution

Field Name Data Type Null Key References Length Description

Course Course name


CourseName String No 50
(name)
Course Course number
CourseNumber String No PK 50
(number)
Assignment Assignment
AssignmentNumber String No 50
(number) number
Start time of the
StartTime Datetime No PK 8
assignment
End time of the
EndTime Datetime No PK 8
assignment
Uniform resource
locator of the
ScriptURL String No 50
script
file (NANT)
Uniform resource
BatURL String No 50 locator of the
batch file
notes String Yes 100 feedback
Task 5

Base on the design, Implement a .NET programming solution. Provide


appropriate conclusion including program strengths, weaknesses and
enhancement that can be accomplished with the given solution.

Strengths and weaknesses

The offline and online options available for the LMS allows learners to access learning resources
with limited internet connectivity. Such learning content consistent with includes videos, e-library
(e-books, e-journals, and databases) and lecture notes. These flexibilities of the system open doors
for instructors to extend their capacity of learning and learners to attenuate costs.

Human resource- human resource consists of top management, Coordinator, students, etc. who
works in a corporation to realize its objective efficiently and effectively and are the representative
of the organization.

Physical resources- physical resources contains location, building, equipment which are the
required resources utilized in a corporation.

Finance- are the grants, funds, and another source of income which is again necessary for a
corporation to figure.

Activities and processes- it's the program which a corporation involve and system they run

Past experiences- past experiences portray the reputation of a corporation, and that they also are
the building block in learning and success.

Opportunities and threats

The economy- it consists of local, national, and international factors which directly affects the
organization.

Demographics- demographics are the changes within the race, age, gender, or the prevailing
culture.
Task 6.

Analyze the events and control structures you identify in implementing the
proposed design with valid examples, taken from the system.

One of the most convenient aspects of the new ASP.NET Web Forms model is that it brings event-
driven programming, popularized by Visual Basic, to the web world without all the kludges of the
late unlamented Visual Basic Web Classes.ASP.NET has a number of built-in events at the page
level for which you can write event handlers to execute code.

Moreover, most server controls expose one or more events for which you can write handlers. Table
5-8 shows a list of common events and the controls that support them. These events and controls
are in addition to the standard events, such as Init, Load, Prerender, and Unload, that are inherited
from the base Control class.

Button server control exposes the Click and Command events. These events are both raised when
the button is clicked, but while the Click event is usually used simply to handle the event for a
single button, the Command event can be used to handle clicking on several buttons (so long as
the buttons' Command Name property is set).

The CommandName property, along with an optional Command Argument property, become
properties of the CommandEventArgs object, which is passed as a parameter of the Command
event handler. You can then examine the CommandName and CommandArgument properties
within the event handler code to determine what action(s) to take.

Example-1 (Control structures)

While (j < ds.Tables(0).Rows.Count And found = False)


If (ds.Tables(0).Rows(j).Item(1) = Me.txtId.Text And
ds.Tables(0).Rows(j).Item(0) <> "") Then found = True
End If
j=j 1
End While
Example-2 (Control structures)

If (coordinator.Tables(0).Rows(j).Item("ID") = Me.txtuser.Text And


coordinator.Tables(0).Rows(j).Item("Password") =
FormsAuthentication.HashPasswordForStoringInConfigFile(Me.txtpass.Text, "Md5"))

Then
found = True
x = coordinator.Tables(0).Rows(j).Item("ID")
Session("x") = x
Session("name") = teacher.Tables(0).Rows(j).Item("Name")
Me.Response.Redirect("admin.aspx")
Me.lblerror.Visible = False
End If

j=j+1
End While

If found = False
Then
student.ReadXml(MapPath("Student.xml"))
j=0
While (j < student.Tables(0).Rows.Count And found = False)

If (student.Tables(0).Rows(j).Item("ID") = Me.txtuser.Text And


student.Tables(0).Rows(j).Item("Password") =
FormsAuthentication.HashPasswordForStoringInConfigFile(Me.txtpass.Text, "Md5"))

Then
found = True
x = student.Tables(0).Rows(j).Item("ID")
Session("Password") = student.Tables(0).Rows(j).Item("Password")
Session("Email") = student.Tables(0).Rows(j).Item("Email")
Session("x") = x
Session("name") = student.Tables(0).Rows(j).Item("Name")
Session("counter") = j
Me.Response.Redirect("student.aspx")
Me.lblerror.Visible = False
EndIf

j=j+1
End While
End If
If found = False Then
Me.lblerror.Visible = True
End If
Task 7

Error handling is one of the major factors in determining the success of a


software solution. Identify and implement opportunities to apply the error
handling in developed solution.

An exception is an error condition or unexpected behavior encountered by an executing program.


Exceptions can be raised because of a fault in your code or in code that you call (such as a shared
library), unavailable operating system resources or unexpected conditions the Common Language
Runtime encounters (such as code that cannot be verified).

Error handling in ASP.NET has three aspects:

1. Tracing - tracing the program execution at page level or application level.


2. Error handling - handling standard errors or custom errors at page level or application level.
3. Debugging - stepping through the program, setting break points to analyse the code.

Although ASP.NET can detect all runtime errors, still some subtle errors may still be there.
Observing the errors by tracing is meant for the developers, not for the users

Hence, to intercept such occurrence, you can add error handing settings in the web.config file of
the application. It is application-wide error handling.

Example:

public partial class _SSub : Page

protected void Page_Load(object sender, EventArgs e)

if (!IsBack)

{
try

String connectionString=

ConfigurationManager.ConnectionStrings["MyConn"].ConnectionString;

string selectSQL = "SELECT * FROM tblStudents";

SqlConnection con = new SqlConnection(connectionString);

SqlCommand cmd = new SqlCommand(selectSQL, con);

SqlDataAdapter adapter = new SqlDataAdapter(cmd);

DataSet ds = new DataSet();

adapter.Fill(ds, "Students");

GridView1.DataSource = ds;

GridView1.DataBind();

catch (Exception ex) {

// Log the exception

Label1.Text = "Something Bad happened, Please contact Administrator!!!!"; }

finally {

}
Web.config file

Although ASP.NET can detect all runtime errors, still some subtle errors may still be there.
Observing the errors by tracing is meant for the developers, not for the users.

Hence, to intercept such occurrence, you can add error handing settings in the web.config file of
the application. It is application-wide error handling.

Code:

<configuration>

<system.web>

<customErrors mode="RemoteOnly" defaultRedirect="GenericErrorPage.htm">

<error statusCode="403" redirect="NoAccess.htm" />

<error statusCode="404" redirect="FileNotFound.htm" />

</customErrors>

</system.web>

<configuration>
Task 8

Specify how much supportive the .Net IDE in creating a programmatic solution
for the given scenario. Support your answer with appropriate illustrations.

ASP and ASP.Net Web Development Solutions

ASP and ASP.Net are web development models particularly popular with e-commerce sites. They
allow website creation with minimal coding, and although less popular than PHP, have the
advantage of being fully integrated with Microsoft and the Windows server and tools.

This integration means that websites built with ASP.Net can be created, debugged and maintained
within Visual Studio.NET – a very popular development environment.

The Advantages of ASP and ASP.Net Web Development Solutions

• Swift execution – web applications execute more quickly than interpreted scripts.
• Language compatibility – ASP.Net allows developers to write in multiple programming
languages.
• Object Oriented Programming (OOO) – OOO makes it possible to build large web
applications without sacrificing clean coding, by separating code from display.
• Access to the .NET framework – this extends the Windows API.
• Familiar controls – the server controls on a web page look and feel like the controls on
Windows applications, creating a familiar working environment. It’s possible to create new
controls too.
• Support – web services build with ASP.net automatically support XML and CSS, plus
SOAP, HTTP-GET and HTTP-POST protocols.
• Cost – ASP.Net is free with Windows OS.
• Web services feature – the web services feature with ASP.Net means that you can split
several parts of an application across different servers, and the entire application will still
work as a whole.
• Microsoft class library – ASP.Net includes a class library with a wide variety of functions,
reducing the need for code writing.
• Visual Studio – Microsoft’s visual studio is an excellent tool for creating high quality
applications and is only available with ASP.Net.

How they help?

• Quick turnaround time – we work to tight schedules and never miss a deadline.
• Quality not cost – our prices are upfront and there are no hidden charges. You’ll never pay
for something you won’t use.
• Transparent working process – we believe in involving our clients at every stage of the
design and development process, from information gathering to testing.
• Rigorous development testing – our websites go through extensive debugging in the
development environment before we ask you to test them.
Task 9.

For the developed program application; produce a test plan with appropriate
test cases to carry out the testing process and critically analyses your test
results.

Login

Test Number Test case Expect Result Actual Result Test Result

Login without Cannot access Did not access the


01 Test case pass
register system system

System allowed
System want to
the hand phone
allow only hand
number only and
phone number and
Register new send a verification
02 send verification Test case pass
student code to hand
code to hand
phone number and
phone number to
after verification
verify
allow to access
Test description Test Results
1. The user requests the home page from web server.
Function: User requests the page from web server.
Description: This function provides ability to browse the system.
Input: The system URL.
Source: User.
Output: home page. 
Destination: Web server.
Require: Insert correct site address.
Pre-condition: Availability of internet service.
Post-condition: Displaying the system home page.

2. Display Student profile.


Function: Displaying the student information.
Description: By clicking the profile link from the main menu a new page will
be displayed containing the student information.
Input: Clicking my profile link from student main menu.
Source: The student and student menu web form.

Output: The student profile.
Destination: Web server.
Require: Valid log in and single click on my profile item.
Pre-condition: Home Page and no student displayed in main menu. Post-
condition: The student can see his profile.

3. Update student profile.


Function: Update student data
Description: The student can update his information (name, email and

password). Input: By clicking my profile link from student main menu and
entering some specific information to the OSS and saving them in the web
server.
Source: The student and student menu web form.
Output: Save student data in the OSS system.
Destination: Web server.
Require: Valid login and single click on update –my- profile item.
Pre-condition: Student Home Page + having an account on the OSS. Post-
condition: Save data in web server (Student XML file).

4. See the assignment.


Function: Student can see the information about the assignment (description
and instruction, start-time, end-time, motivation, how to download the
assignment and upload it, type of work individually or as groups). 
Description: By clicking the courses link from the main menu a new page will
be displayed, containing courses and related assignments.
Input: Clicking my courses link from student main menu.
5. Uploading the solution.
Function: Upload solution of the assignments.
Description: By clicking the courses link from the main menu a new page will
be displayed, containing the courses and related assignment information, the
student can upload the solution of his assignments before the deadline (if
strict).
Input: Clicking on my courses link from student main menu and select the
assignments from the grid view and upload the solution and saving them in 
the web server.
Source: The student and student menu web form.
Output: Save solution information in the OSS.
Destination: Web server.
Require: Valid login and single click on course link.
Pre-condition: Student Home Page and registered student courses and submit
the assignments before the deadline (if strict).
Post-condition: Save data in web server (solution XML file) and received
message from the system after uploading the solution (accept or reject) when
the teacher make the correction process.
6. Coordinator can add, delete, and update courses.
Function: Add, delete, and update courses.
Description: This function Provides administrator the ability to insert, delete
and update courses.
Input: Click on insert course link from administrator main menu and fill
course name, course number, course credit, course level and the course type
text, or click on update courses link to update course or delete it from courses
xml file. 
Source: Administrator and insert new course web form or update course.
Output: Save the course and its information in courses xml file.
Destination: Web server.
Require: Valid login and single click on courses link (insert or update).
Pre-condition: Admin Home Page and fill all textboxes with valid data type.
Post-condition: Save courses in simple course xml files or update it.

7. Coordinator can upload a test Ant/Nant script for testing the assignments.
Function: Add Ant/Nant script for testing the assignments.
Description: This function Provides administrator the ability to upload a test
Ant/Nant script for testing the assignments for all students.
Input: Click on correction link from administrator main menu and select the
Course name and the assignments to upload the script text.

Source: Administrator and upload Ant/Nant script.
Output: Save the Ant/Nant script and its information in correction xml file.
Destination: Web server.
Require: Valid login and single click on correction link.
Pre-condition: Admin Home Page and fill all textboxes with valid data type.
Post-condition: Save Ant/Nant script in correction xml file.
8. Coordinator can manually send feedback, marks and notes to students.
Function: Send feedback and notes to students.
Description: Administrator can provide students with the feedback and notes.
Input: Click feedback link from administrator main menu.
Source: Administrator and feedback web form.

Output: Display feedback and notes for students.
Destination: Web server.
Require: Valid login and single click on feedback link.
Pre-condition: Admin Home Page and fill all textboxes with valid data type.
Post-condition: Save feedback and notes in correction xml file.
9. Generate reports
Function: Generate reports
Description: Teacher can see the assignments submitted by students. He can
assess the students by browsing a report of the assignments and students.
Input: Click on report link from administrator menu.
Source: administrator and report web form.

Output: Report on student data and evaluation of home assignments.
Destination: Web server.
Require: Valid login and single click on reports link. Pre-condition: Admin
Home Page.
Post-condition: Displaying students

10.Insert Marks
Function: Insert marks.
Description: This function Provides administrator the ability to insert marks
of courses offered at the end of current semester.
Input: Click on insert marks link from administrator menu and choose the 
course number and student number then insert marks. Source: Administrator
and insert marks web form.
Output: Save courses marks for each student registered in the previous
specified course.
Destination: Web server.
Require: Valid login and single click on marks link.
Pre-condition: Select course number and student number.
Post-condition: Display students and insert marks saved in registration xml
file.
.
Task 10.

Provide the implemented system to someone else (may be your friend) get their
feed about your system. You have to include copies of questionnaires you
provided to them as evidences. Write a small report on how you plan to improve
your system further more based on the findings you made.

Questionnaire

Here we will distribute the set of questionnaires so that it will be easier for us to collect the actual
data. For this questionnaire we are going to take question no. 3 from the selected questions and
our target clients are university lecturers as the number of the lecturers are large in groups. The
questions will be passed to the lecture to know the actual requirements and their expectations
towards the system when they log in. The questions will be highlighted the areas of functionalities
after they login. Besides, it will also provide the UI (User Interface) related questions like what
they prefer from feedback panel after login. For this technique we will select maximum 3 lecturers
from each department and gather the actual requirements regarding the feedback system.

Based on the questionnaire we will be able to identify the requirements for designing the system
and gather the data to improve the overall functionalities.

Observation

This technique is used to observe the users while interacting to the system or any situations. To
conduct this technique, we are going to take question no. 1 from the selected questions. Here we
will observe how the students and the lecturers are communicating using the current system. It will
show whether implementing the new system will be helpful for both lectures and students as well.
This will help us to collect data about some cons of the current system as well as how we will be
able to improve the proposed one. On the contrary observing the student’s activities towards
assignment submission in a particular time will help us to know usually when the students gather
from different departments in one area to submit their assignments.
Research question

Here we can divide the research question into two specific fields. They are:

1. Domain Research Question


2. Technical Research Question
Below we are going to listing out the domain and technical research questions which will be helpful
for the further designing the research and describing the literature review as well.

Questionnaire that given:

Domain Research Questions

1. What to expect in UI (User Interface) while logging in to the system from both students and
lecturers’ panel?

2. What should be the storage requirement for the database?

3. Is this system will be helpful for the students as well as lecturer in future?

4. Is the system should be available 24 * 7?

5. What lecturer expect when they login to the system?

Technical Research Questions

1. What programming language (VB, C#) should use while developing the system?

2. Which framework (PHP / .NET) user prefer to develop the system?

3. Which database (SQL SERVER, MYSQL, MONGO DB, and ORACLE) should integrate with
the system?

4. What kind of authentication (ASP.NET MEMBERSHIP) should be implemented into the


system?

5. Which scripting language (JavaScript, VB Script) should use for developing the system?
Task 11.

Create a user document (User manual) for the developed solution to assist the
users to work with it. Brief explanation and screen capturing would be helpful
in this section.

User document

In online assignment submission number of forms considering user friendly and interface
consistency is designed, by using the standard web methods and tools in the ASP.Net such as
master page and web user control and cascading style sheet.

Login page

This page is enabling the student, coordinator, and administration to access his account, see his
data and use menu by using valid username and password.

Figure 15
Add new student page

This form enables the instructor to add new students to the database, keeping in mind that the
student ID should not be repeated more than once.

Figure 16

Edit student page

The form also enables the instructor to revise student data and or delete students from the database.

Figure 17
Add new course page

The form enables the instructor to add courses to the database, keeping in mind that a course code
or number should not be repeated more than once, since this code or number is a primary key.

Figure 18

Add new course page

The form enables the instructor to add courses to the database, keeping in mind that a course code
or number should not be repeated more than once, since this code or number is a primary key.

Figure 19
Registration page

The form enables the instructor to register new students to available courses. In this case, both the
student number, the number of the study course as well as the date of registration is considered
primary keys.

Figure 20

Report

The form enables the instructor to compile student reports and know those students who have
sent their home assignments and those who have not. It will also allow him to know how many
times a given student has tried to upload his assignment before the expiry of the deadline.

Figure 21
Add assignment page

The form will enable the instructor to add fresh home assignments to the database, keeping in mind
that the assignment code as well as the start-time and end-time should not be repeated more than
once since these are primary keys.

Figure 22
Student profile page

This form enables the student to update his information (name, email, and password).

Figure 23
Task 12. Provide a suitable technical documentation which covers designs,
platform, file structures, and instructions for maintenance.

ASP.NET Core's built-in use of and support for dependency injection makes this architecture the
most appropriate way to structure non-trivial monolithic applications. For monolithic applications
the Application Core, Infrastructure, and UI projects are all run as a single application.

Most traditional .NET applications are deployed as single units corresponding to an executable or
a single web application running within a single IIS app domain. This is the simplest deployment
model and serves many internal and smaller public applications very well. However, even given
this single unit of deployment, most non-trivial business applications benefit from some logical
separation into several layers.

The smallest possible number of projects for an application architecture is one. In this architecture,
the entire logic of the application is contained in a single project, compiled to a single assembly,
and deployed as a single unit.

A new ASP.NET Core project, whether created in Visual Studio or from the command line, starts
out as a simple "all-in-one" monolith. It contains all of the behavior of the application, including
presentation, business, and data access logic. Figure shows the file structure of a single-project
app.

Hardware Requirements

• Pentium 4 computers or above.

• Basic Printer for report printing.

Software Requirements

• Any Operating Systems (Windows/ Linux/ etc.)

• Any Web Browsers (Google chrome, Firebox, etc.)


Figure 24
Task 13:

Assignment Gantt chart should be realistic and reflect the management of the
activities. Furthermore, the challenges faced when trying to achieve the
milestone need to be explained.

1st Week 2nd week 3rd week


Activity
1st 2nd 3rd 4th 1st 2nd 3rd 4th 1st 2nd 3rd 4th

Title

Collecting
Information

Background
Study

Planning

Designing

Implementati
on

Integration

Testing

Operation
and
Maintenance

Documentatio
n
Challenges faced when trying to achieve the milestone

• Time Management
• Conflict and tension.
• Low engagement.
• Lack of transparency.
• No long-term thinking.
• Badly perceived, not delivering.
• Poor change management.
• Poorly Defining the Goals and Objectives.
• Unrealistic Deadlines.
Task 14: Appropriate security features, such as login screens and role-based
security can be incorporated and openness to new ideas to indicate the creative
and innovative thinking of the student.

One of the common problems faces by most of the industry is integrating a completely new system
within the existing system. The reason behind is that they are already used to with the existing
system, so changing to the new system they needed to be trained up.

Students facing some problems while following the current system of assignment submission. As
the university, does not have any system where students can submit their assignment online,
students need to undergo some rules and regulations. To submit their assignments, they need to
print and do cover binding from the printing stations.

Currently, the cost of papers as well as printing is much costly compare to any previous time in
Malaysia. So, students need to pay from their pocket money for printing and binding which is
costly. Along with that, they need to buy CD and attach with their assignments as a softcopy of
their entire working projects. Sometimes students need to wait in a long queue in front of printing
stations which is also time consuming.

As result, some students fail to submit their assignments on time. Moreover, it seems on the peak
hour time, students from different departments gather at admin office to submit their assignments
which deteriorate the entire environment.

It is because admin office deals with local and international students those are having problems
with academic results, attendance etc. so there is always a chaos at admin office. Students also
need to provide CFF form where they need to write details such as name, id, module name,
lecturers name etc. as a reference for the admin so that they can pass the assignments to the right
lecturer on time.

Sometimes students need to buy from admin office if they forget to bring along with them which
is costly for students. Admin plays an important role from receiving assignments until publishing
on student’s portal. As they also follow the current system, they need to go through some
difficulties while dealing with student’s feedback regarding the assignments, modules or lecturers
teaching quality.
Although students sometimes launch complain, admin can’t track the improvement of the facts
which will ensure the elimination of the complaining materials.

So, there is hardly any follow up for the improvement of student service by admin panel. Moreover,
less of evidence from student’s side has also become facts where admin cannot take decisions
whether they will call a board meeting to eliminate the circumstances or not. To be added, some
students visiting admin office just for no reason also waste their time.
Conclusion

This project is aimed at downloading and uploading online assignments for students, with each
assignment having information about the instructions, description, deadline, and submission
details.

The main goal of this project is to design and implement online assignment submission and provide
an interface use for uploading test program by instructors, who would be able to evaluate
assignments automatically.

The most obvious advantage offered by online assignment submission is that it offers faster
transmission of assignments than using traditional way by using online system. The interface use
to invoke different testing program by teachers, So Save the time and cost for teachers by enabling
them to put up a fast response for students as well as increasing the quality of the feedback provided
to students.

You might also like