web_projects_policy_fall08.09

handslustyInternet και Εφαρμογές Web

14 Δεκ 2013 (πριν από 3 χρόνια και 10 μήνες)

77 εμφανίσεις


WEB PROGRAMMING


Mohammad Amin Kuhail

M.Sc. (York, UK)





Projects Directions









University of Palestine





Faculty of Applied Engineering and Urban Planning





Software Engineering Department





Faculty of Information Technology


Available from: THU,
02.11.08


Available until: WED,
24.12.08

Pr
ojects Directions



Outline




Projects Guidelines




Project Structure




Project Phases




Documentation structure




Submission




Grading Policy




Students out of Gaza




Projects statement




Final word for my students (in Arabic)










Projects Guidelines













1.

We have two teams. Each one consists of four students.


2.

Each team shall choose a name.


3.

Each project shall have a team leader.


4.

Each team member shall be assigned a task in the project, and shall be
knowledgeable to all aspects of the project.


5.

Pr
ojects will be distributed on students randomly on Wednesday

05.11.08
.


6.

You shall present your project on the submission day.


7.

You shall submit a CD that contains (Project report + Source code +
Presentation file)






Projects Guidelines


8.
You shall demonstrate your working source code to the teacher on the
submission day.


9.
Any plagiarism will be extremely punished (Reference anything you copy).


10.

You shall meet your customers regularly to keep them up with your progress.
Please note I will be asking them about every team mate’s performance to
check how much serious you are about this project. Make sure you behave well
with your customers. Adhere to appointments please.


11.

Your projects will be real
-
like projects. That means you are going to work on
real projects for real customers who actually need these projects. The
customers are employees at the University of Palestine. Your project will
certainly get used and might get published on the internet if it is of high quality
so it is a promising chance for you to prove your qualities.


12.

EVERY TEAM MATE MUST WORK. I WILL SEVERELY PUNISH
SLACKERS!!!







Project Structure







Every project must have the following basic elements:


1.
Plain Layout:




A plain XHTML code which is your basic layout for the project.


2. Style




CSS external file(s) to set the decorations and effects for your project.


3. JavaScript (Only if you need to)



JS external file(s) for any necessary client side programming.




Project Structure








Every project must have the following basic elements:


4. Dynamic part:




your PHP + mysql code which will act as the dynamic part for your website.





Project Phases










Every project is divided into four phases during which I will check up
on your progress.




Phase 1: Project Understanding: (12.11.08): I expect you to:




Present your understanding of the project( Include description, requirements,
plan, expected challenges)


Discuss any problems you faced so far.




Phase 2: (Your design) XHTML+CSS : (19.11.08): I expect you to:




Feedback from phase 1 shall be taken into account.


Present What you did( justify your design choices on web usability issues, color
matching, etc)


Demo your working version of what you did.


Discuss any problems you faced so far.





Project Phases





Phase 3: Project Final Polish of the client
-
side scripting and design:
(26.11.08): I expect you to:




Feedback from phase 2 shall be taken into account.


Present what you did( Include the final touches on your web design. Highlight
web usability issues and you took comments from phase 2 into account).


Discuss any problems you faced so far.




Phase 4: Your v1. dynamic web based application(3.12.08)




Feedback from phase 3 shall be taken into account.


Present What you did( In addition to your working dynamic work, You should
come up with a main class diagram as well as a general outline of what you
intend to do as well as database choices )


Demo your working version of what you did.


Discuss any problems you faced so far.





Project Phases


























Phase 5: Your final version of your web based application(17.12.08): I
expect you to:




Feedback from phase 4 shall be taken into account.



Present What you did( justify your web dynamic programming as well as
database choices )



Demo your working version of what you did.



Discuss any problems you faced so far.




Final Presentation day:




You shall submit your final source code along with the required documentation
on a CD as well as the UPINAR.


Present What you did( Justify your choices )


Demo your working version of what you did.



Your customer will be present to watch your presentation and the demo of the
work.







Documentation structure














You are required to submit two documents:


1.
Project Report which contains: (from 20 to 30 pages):




Introduction

(Introduce your project and highlight its main goals, also
mention your project organization (team mates, team leader, and rules of each
one).



Requirements

(List what your application intends to do. In other words, list
what you are required to do).



Solution

(state your design ideas (include pictures of your layout design as
well as style effects. Justify your choices), your development design (Highlight
significant bits of code as well as your class and ER diagram) ).


Conclusion

and Learning outcomes



Further Work.





Documentation structure










2. Personal Essay which contains: (no restrictions on number of pages):




Since it is a personal essay, only one individual shall write his or her personal
essay. You can write anything you want about:




Your personal experience during this course. Did you enjoy it? Do you feel
different after taking this course?



The way the teacher taught it.



Did you enjoy working on the project? Was it fair? Was it a lot of work? Was
your customer helpful and co
-
operating?



The way your team mates co
-
operated with you, and the way you did with
them.



How could the teacher or the University of Palestine have made it a better
course?



Anything else.




Note: Please be sure that I WILL NOT PUNISH YOU IF YOU
CRITICIZE ME OR CIRITIZE ANY MEMBER AT THE UNIVERSITY OF
PALESTINE.







Submission








Two days before the submission day (22.12.08):


1. On the UPINAR You must submit:




Project Documentation (Project report + Personal Essay).


Your web application (source code + a simple manual stating how to run it).





On the submission day (24.12.08):


1. On a CD You must submit:




Project Documentation (Project report + Personal Essay).



Your web application (source code + a simple manual stating how to run it).



Your presentation file.



Grading Policy














20
%:

Documentation:




35
%:

Quality of the solution



10
%:

Documented source code




15
%:

Presentations




20
%:

Fulfillment of the customers requirements




+
10
%:

If your project gets used.





Project Client














Client Name:
Mohammad Temraz.


Department:

Software Engineering Department.


URL:

http://swe.up.edu.ps/academic.php#mat








Project Statement







E Article






You shall develop a web based Article System for the Software Engineering
Department that does the following tasks:


1. Presentation:



The end user shall be able to see articles archived in several categories.


Categories can contain categories as well.


Topics should be listed alphabetically, or according to date, ratings, or by most
read. [Perhaps grids is a good idea to visualize this

http://www.extjs.com/products/extjs/
]




End users shall be able to comment on each article. However, comments can
not be show till the administrator approve them.




End users shall be able to view the author information.


Each article has a topic, sections, and can have links or images inside. Take a
look at how articles are written out in wikkipedia.






Project Statement







E Article







Each article can contain a simple table of content to highlight its main sections.


If article is edited, or collaborated it shall be noted.




Authors can add/edit/ articles.



Articles contain rich text, inks, tables, images.


Images should be saved in a folder dedicated for that user.





once articles are published by administrators, authors cant edit them.



Author shall add/edit their personal information as well as digital photo.






Project Statement







E Article





2. Administrators.




Add/delete auth
ors.


Publish/Unpublish articles.


Archive articles.


Publish/Unpublish user n
otes.


Review s
ome stastical information such as:

Number
of anynamous users read an article.



Review s
ome stastical information such as:

Number
of anynamous users read an article.








Project Statement







E Article





2. Users/Anonymous users/Other Authors:




Shall be able t
o comment on author/s article.


Shall be able to rate an author/s article.





















Good Luck