Prototype of the System 09 6. Web Design Project 1. Introduction Online photo processing system software is a commercial product for the normal user to get digital photo printing service. This document is provided for the requirement and design specification so that developer can get the clear idea of the system and also the design specification of the system.
It contains also prototype UI which is very useful for the customer to know about front-end view. Business requirement Printing digital photos through online print shops is significantly gaining market. Typically, print shops only offer payment via credit card and automatically apply standard picture settings that not always produce acceptable results. To guarantee professional service, higher quality and flexible payment options, the following procedure to be automated could help.
A user starts the processing by logging user name and password in the system. Immediately, the system checks whether the uploaded files are compatible picture files and whether the pictures' resolutions are suited to the specified print sizes.
In case of problems, the user is asked to modify his order. This procedure goes on until no further problems can be detected, in which case the order is forwarded to a photo editing expert, which is in charge of checking the aesthetic quality of the pictures. Based on the user's decisions, the expert applies the accepted modifications and fixes the final cost. Once the cost of the order is known, the system sends an email with the required payment instructions to the user and, also, forwards the pictures to the print department.
The user can choose between online payment via credit card, money order or bank transfer. Credit card payments are directly supported and processed by the shop's Web site, while the two other options are not under control of the system, which thus keeps waiting until the payment occurs.
After completing the payment terms, system will ask for the shipment address. In the meantime, the print department prints the pictures and prepares them for shipment. Once the payment has arrived, the prints are shipped, and the user has one month to provide his feedback and to close the order before the process terminates automatically.
Mohammad Jannatul Ferdous 5. Web Design Project 3. UML Design 3. Web Design Project The Use case diagram of the online digital photo processing system contains the scope of the system, the list of system functionalities and the total vision of the possible interactions between the system and the actors of this system.
The main actors identifying here are: i Customer: Customer represents as the primary actor for this system. The printing company offers the digital photo printing service online for the customer in different location.
General Operator: This type of actor supports the system to complete the main flow of events to achieve the goal. It takes care to delivery the shipment order to the requested customer. Administrator: Administrator of the system is responsible to several interactions with the system to reach the objectives. As an example administrator can delete the customer order at any time with proper reasoning. Based on the above use case diagram we can identify the following groups of main types of activities: i.
Customer starts the processing by logging in the system. The system checks the picture files with respect of compatibility and resolution suited to specific print size. This procedure goes on until no further problems can be detected. The expert applies the accepted modifications and fixes the final cost.
The system sends an email with the required payment instructions to the user and forwards the pictures to the print department. Credit card payments are directly supported and processed by the shop's Web site. After completing the payment terms, shipment address will be collected.
The print department prints the pictures and prepares them for shipment. Once the payment has arrived, the prints are shipped, and the user has one month to provide his feedback and after that the process terminates automatically.
Mohammad Jannatul Ferdous 7. It is built and refined when system is developed. Each class description consists of a class name, state variables, reference variables and methods. We make a clear distinction between variables containing the state of an object and variables that express which other objects a given object knows.
A class description defines the types of each variable as well as a signature for each method. The objectives of class diagram are. Names and models concepts existing in the system. Specifies collaboration paths. Specifies the basic logical schema. Mohammad Jannatul Ferdous 8. Web Design Project In On line photo processing system, the front view of class diagram is shown in the above figure. The class diagram are composed of several classes and there relationship between these classes.
Framework of the development 4. Those are: Mohammad Jannatul Ferdous 9. Introduction Web Development On Web Introduction 1. Introduction 1. Existing guidelines for Web usability hinder web-based application usability since they are primarily based on interactions within a browsing metaphor.
The main difference is that with traditional in-house software the user only focuses on the application itself. The application is stand-alone, installed on the users system and the IT department or network administrator takes care of the management, monitoring, updates and all other tasks related to using software in a business environment.
A SaaS Software as a Service [2] application also focuses on this primary application part, but incorporates tasks that all together make up the SaaS application and business model. These tasks include registering, paying for the software, using support and customizing the application. A SaaS application is much more specifically directed to the customer instead of a traditional desktop application directed at the mass.
This results in a higher value of design and interaction. With this software, websites can be designed in cloud without the requirement of costly website designing softwares and installations.
It will provide a user friendly dashboard which will serve for all user needs. All the HTML tags may be implemented. Thus, user can create web page without learning HTML. Especially these properties differ SaaS from standard web-based software. SaaS is a model of software deployment where an application is hosted as a service provided to customers across the Internet.
Using SaaS also can reduce the up-front expense of software purchases, through less costly, on-demand pricing [3]. Web Development On Web Introduction By implementation of the WebyWeb project, we aim to take the above concept further and provide the user with the ability to develop web pages on internet without having the need of installations of the softwares that facilitate this process.
It is a self contained product which provides improvement in the current web development scenarios. Therefore, WebyWeb will support undo and redo. User manual will be provided for easy work environment. This assumption holds true for those areas of IT that are ubiquitous, a cost of doing business and commodity-like.
SaaS is therefore not suitable for innovative or highly specialized niche systems, though SaaS may be used to provide one or more components in such systems.
Silverlight 2 plug-in installed. Web Development On Web 1. Since Silverlight provides rich web based interactions, resolution of screen and graphics aspects of hardware are extremely important. Installations of Microsoft expression blend, visual studio , Silverlight are essentials which enable the developer to develop their application. Project Plan Provide project oversight and guidance.
Deipali Gore External Guide Mr. Update plan regularly. Identify and resolve issues. Identify and mitigate risks. Deipali Gore Mr. Requirement Analysis Requirement Analysis 3. But disadvantage with them is that they need installations on the respective machines. With this, the WebyWeb editor is centralized on server thereby eliminating the need to install the application.
All the updations are centralized for maintaining consistency and thus reducing the overhead for client to update the software individually. Payment will be done on the basis of package that will be subscribed for. WebyWeb can be used by any novice user who has minimum technical knowledge about web page development. With highly user friendly and rich graphical environment, the experience of web page development will be enriching and easy. WebyWeb provides implementation of all the basic html tags.
Insertion of form elements like buttons, checkbox, images, tables etc is provided. Easy navigation from design to code view check the code generated for the corresponding web design.
It is recommended that the SRS document is read sequentially. It enhances the user work experience by providing aesthetic environment. The software WebyWeb will revolutionize the way web pages are designed.
All the HTML tags and scripts may be implemented. For developing any web page, many softwares are available like Dreamweaver etc. But disadvantage with them is that they need installation, payment is expensive and a user that need not use high end functionality has to pay complete cost of the package. Moreover, coding knowledge may be required to use these softwares.
By implementation of the WebyWeb project, we aim to change the scenario by allowing user to develop web pages on internet without having the need of installations of the softwares.
Implementation of basic HTML tags and insertion of — a. Images c. HTML form elements radio button, checkbox, button. Rich Text formatting. WebyWeb has dual interface showing design view as well code view. Thus amateur users will not find it difficult to design their own web pages. Using design view they can make the website the way they want. On the other side expert users have an added advantage of knowledge about coding.
It is cross browser can be run on most web browsers including Internet explorer, Mozilla, etc. Installations of Microsoft expression blend [8], visual studio [9], Silverlight are essentials which enable the developer to develop their application.
Silverlight 1. The PC is connected to internet. This means that the web page designer software has a user friendly interface. The user just has to imagine the look of the page and may design it just as designing on a piece of paper. Using tools provided by the software. The coding details are hidden, making it possible for non-coders to create web pages and sites.
It includes a menu bar, tool box, properties window, status bar. It fragments the incoming byte stream into discrete messages and parses each one on to the internet layer. At the destination, the receiving TCP process reassembles received messages into the output stream. TCP also handles the flow control to make sure a fast sender cannot swamp a slow receiver with more messages than it can handle. Its original purpose was to provide the way to publish and retrieve HTML pages.
The originating client, such as web browser, spider or other end user tool, is referred to as a user agent. The destination server which stores or creates resources such as HTML files and images is called the origin server.
In between the user agent and origin server, any is several intermediaries such as proxies, gateways, tunnels. An HTTP server listening on that port waits for the client to send a request message. The time between request and reply should be less in case of online help. Minimum time should be taken by the application to display preview the web pages developed by the user. In case of power failure, the data should be stored in the state that was last saved by the user.
A firewall should be present for packet — filtering and other security issues. Availability — As WebyWeb is a web based service provided to the users, it will be available as long as server is up. Interoperability — WebyWeb is interoperable on various operating systems, thus increasing the applications usability and flexibility.
Maintainability — WebyWeb is a SaaS based service. Hence, all the updates are centralized making the maintenance convenient. Creative — Users can apply their imagination in full extent thus enhancing their creative power without actually worrying much about the technical details. It is based on cloud computing.
Architecture is divided into two parts namely the database and the main editor. The project resides on WebyWeb server. In our system, there's a significant workload shift. Local computers no longer have to do all the heavy lifting when it comes to running applications.
The network of computers that make up the cloud handles them instead. Hardware and software demands on the user's side decrease. The only thing the user's computer needs to be able to run is the WebyWeb's interface software that is in a xap [9] file which is loaded on client PC on fly as the user accesses the WebyWeb website.
They connect to each other through a network. The Main Editor is the side the client operates on. This includes the code conversion engine, Dashboard interface, User Workspace area. The database is the section which maintains the user information, files and log. Storage devices are required to keep all clients' information.
Our system will make a copy of all clients' information and we will store it on other back up devices on daily basis. A communication matrix defines the communications requirements in the project. It describes communications rules and the process of holding meetings. It ensures every meeting successfully serves the purpose of holding it and get desired result. While communicating with the stakeholders the structure of the project team should be presented. The Communications Matrix has defined the communications requirements.
To determine what information to present the communication matrix will be used. What to communicate, to whom to communicate and when to communicate is described in the matrix. The communications should be short and brief unless they want more information. Project manager and members should only communicate if the sponsor asks for.
Technical designs, implementing design and documentation. He will communicate closely with the project manager and project team. He will communicate with supervisor and project manager.
They need know whole project plan, progress over the time and possible changes in the system the department now work with. They will be kept in touch by the supervisor and project manager.
Also the CPanel they think better should be chosen. In these regards the need to be in close touch with project team. Also enough training should be given to them. They will be briefed by the senior web-designer.
This will be used as the address directory. It should include the topics, presenter and time required. A review and comments on last meeting should be discussed at the beginning of every meeting. Additional time should be kept after the presenters time requirements. It will also take into account the discussion time and review time. It should be suitable for every participant. The ideal place should be in the campus of Jahangirnagar University. Action items are recorded as per agenda and time duration.
Meeting should start with the review of the action items of the previous meeting and end with the decisions taken on the current action items. The owner of the action items should be identified at the review of each new action items.
All the important items discussed in the meeting should be well documented. The record keeper will hand over the record to 47 the chairperson. The project member will then pass it to the project manager and other members if needed. The project manager will then take necessary steps to resolve the issues.
Before making any changes the team should discuss with the stakeholder. It also suggests that p oje t management team is well aware of the risks and it is possible to take actions to prevent these. The site will be used both by students and non-students.
So there is a great uncertainty whether the outside users will get what they are looking for. The project team will work with limited resources and time. To finish the project on time and efficiently, risk mitigation is an important task. The risks that are most probable and has highest impacts is stated here in this schedule so that the persons responsible can take preventive measures early to reduce the risk.
The meetings are arranged to give updates on the risks to the stakeholders and the sponsors. It is necessary to provide reports on the risk management if it is significant. The project manager and the members are responsible for these reporting. Once completed the project team will assess what risk factor arose and how they handle the risk.
They will also analyze the outcome and check if there is any scope for improvements. He will be responsible for monitoring the project risks and plan strategies to mitigate the risks. Project performance such as budget, scope and milestones.
The senior web programmer is an experienced professional in the field of web programming. He will take strategies to mitigate risks related to technology and web development. These risks are mainly the performance of the web site and backend programming.
The central role of risk manager will be mainly played by the Project Manager. To get desired result it is important that all the actions taken is rationalized in the meetings and other form of o u i atio. Also the p oje t is highl depe de t o the sepa ate tasks. It is also required to clarify the requirements by the next phase. Also miscommunication can create negative impression on the stakeholders.
Miscommunication can lead to outputs that are incompatible with other phases. Without good communication this type of problems has a high chance of happening. Potential Response: Arrange meetings regularly and timely. Give everyone space to present their opinion. Prepare adequate documentation to clarify the matters.
Provide everyone with communications list so that anyone can connect to anyone directly. The stakeholders will accept the project, so they needs to know what outcome will the project produce. Unless may not like the outcome. Therefore underestimating the outcome the project team may not get adequate support, resources or time to finish task in time and with satisfactory quality.
Potential Response: A direct communication option among the sponsors and project team can eliminate this risk. Apart from that a meetings will be held to get a better communication and eliminate any misconception.
These types of changes may ruin total project. As every phase of the project is linked with the previous parts. A major change may require changes that are almost impossible to do. For example, changing any functionality of the website may impact graphics design, web design, web programming, backend programming and resources needed.
These type of modification will take great toll on the project team. Potential Response: Paper works of scopes and project requirements should be documented properly and signed by stakeholders.
There should be documentation for the situation if any major changes is demanded. It should state the additional time and other resources. If any bug is discovered it can delay the completion of the website. It is also possible that a bug in the core can lead to a complete overhaul of the website. These bugs can occur by human errors, development tools or hardware. Potential Response: The project has two main resources to do the job. Senior Web Programmer and Tommatos technologies Ltd.
Both are experienced in their field. So it is expected they have the ability to identify the problem as early as possible and fix it. It takes time and money, the project team has provisions for that.
We can also appoint external programmer to assist in debugging procedures. Example of Low priority items are; wrong image, wrong description etc. On the other hand High priority items are difficult to fix and takes long time to debug e. Responsiveness, Backend error, database problems etc. Potential Responses: To avoid these problems it is necessary to take great care while handling high priority items and consume less time on low priority items.
It is also important to identify major features of the website in planning phase and sign them by the stakeholders. The high priority items should be defined by the senior Programmer at the beginning of the project, so that persons involved in these task can be cautious while doing them.
Supervisor, Project Manager and senior web programmer are the key players. Potential Response: The team has been designed in a way that we have backup for almost e e ke pe so el.
O the other hand host party can do the tasks of senior web programmer. In absence of the supervisor chairman or any faculty member can take the responsibility.
To identify risks we will use Crawford Slip Method. It is very common and effective information gathering technique. In this method a small slip is passed to the participants of the meeting and they are asked to write suggestions on a specific questions. It is important that suggestions for only one question is written on one slip. In this project at the risk assessment meeting we will use this technique to identify risks.
We will pass slips at the beginning and everyone will be asked to write as many risks they can regarding the specified topic. Then it will be collected and presented in front of them via projector and start discussion how to eliminate these.
These will also be recorded in the project plan and risk register. All the risks related to the current phase of the project is discussed in the each meeting. The project manager, senior web programmer and members will discuss the risks and their current state. Risk monitoring is a part of monitoring and controlling.
It will be continuous process over the project life. As each risk approaches it will be updated in the risk register. These items will be registered to the risk register and will be included in the risk management plan. It will provide information whether the risks are being identified in time and handled in a professional manner. It is important that current and future risks are managed within the scope, time and resources. The project manager and senior web programmer will analyze the risks and find best way to mitigate or avoid them.
If it is impossible to overcome this should be considered as constraints of the projects. To meet the project time and scope it may be necessary to add extra resources and time. This should be only done in the worst case scenario. Scope and funding should only be modified in the case where no mitigation and avoidance techniques work. After implementation of the project the results are acquired, but some task remains still working. These small task continue to the last phase and continues until they are fully closed.
At maximum it can be delayed to this closure phase, no further. Any unsettled issues or any official paper work should be done in this phase. This will help find any lacking or problem with execution of the project. It will help to organize later project. The form of the closure report is given in appendix 9. Modifications may be necessary to fit the project with the organizational structure of the Department.
Some major items has been presented in the appendix section. It has been separated from the main report for convenience of access. It is possible to complete the project with less cost but as institution that has great reputation should not take too much risk.
Buffer time and backup resource person has been considered to avoid any unwanted delay and p o le s. Larger and sensitive data will be kept at the local server for safety. It will reduce load on main site and diversify the used load on the site.
0コメント