Portal and Intranets
•Download as PPTX, PDF•
2 likes•216 views
The document outlines the development of a portal for XYZ Company. It will include components for employees, customers, and suppliers. The portal will be built using Salesforce and include features like Chatter, files/libraries, profiles, and customized taxonomies for different user groups. It describes collecting requirements, designing system architecture, developing beta versions, and testing. The portal will use cloud infrastructure for availability and scalability. Various APIs will connect components, and security measures like permissions and authentication will protect sensitive information.
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (13)
Similar to Portal and Intranets
Similar to Portal and Intranets (20)
Recently uploaded
Recently uploaded (20)
Portal and Intranets
- 1. Portal Final Project Redar Ismail Intranets and Portals Professor Javid Iqbal
- 2. Our XYZ Portal Building a web portal for XYZ. The portal will be used by companies. • Employees • Customer • Suppliers
- 3. Content • Requirements. • Component Explanation. • System Architecture. • Taxonomy. • Security. • API Lists. • Development Life cycle. • References. • Screenshots.
- 4. Customer • Collecting the requirements of the customer. • Studying the requirements of customer. • Understanding the contents. • Understanding the roles of the customer in portal. • Setting up the permission level for customer. • Deciding the placement of the layout in the portal system. • Security issues discussion.
- 5. Customer • Capacity and Backend Organization • Enable customer portal • Create the profile and organize it. • Create the community • Add the customers to the community
- 6. Employees • Collect the information and start the meeting with IT group. • Convert the needed written data into digitalized data. • Distribute the departments into sections. • Determine the role of each department company. • Identify the type of connection between each department. • Determine the role of the executive. • Design the taxonomy.
- 7. Employees • Implement the portal beta edition • Train the employees about the use of the portal • Make the employees aware that they go through each piece of information. • Update the portal and send notification about each updated made in the portal.
- 8. Suppliers • Collect the information and meet with IT. • Identify their role in the portal. • Identify the communication tools for suppliers. • Discusses the security issues. • Design their taxonomy • Customize the type of layout and menus. • Type of product they offer • Type shipping they use
- 9. Suppliers • Transaction way. • Their way of communication. • Customization of their page • Send the portal guideline if the suppliers was far away otherwise open training session and teach them the use.
- 10. Screenshots
- 11. Portal User
- 12. Portal Users
- 13. Customer, Supplies, Employees Component • Cloud is used for availability, scalability, and reliability. • Cloud help to resolve the expansion. • The backend solutions is mostly used be the salesforce group. • Backend security of the cloud is managed by salesforce it self. • Database environment is created by the salesforce. • Database environment is managed by salesforce. • Content is meta content is created by salesforce.
- 14. Customer, Suppliers, Employee • Different security methods will be used such as secure login page, mobile verification, IP restriction. • Identifying the role and set permission for all portal users. • Social Media gate ways for communication. • Chatter API for group gathering. • Different API is used to deploy use easiness. • Different tabs will be created and pages assigned to it. • Different application used and assigned to the user.
- 15. Customer, Supplies, Employees Component • Document and Libraries • Chatter and Social Media Connection. • Content Management and Ideas Share. • Mobile Organization. • The Use Of API • Supporting Transaction Methods • External Application.
- 18. Taxonomy customer Home Cases Orders Feedback Group Shipment Customer Profile Name Setting Log out
- 20. Employees Home Chatter Cases Contacts Ideas feedback Dep A Dep A Dep A Dep A Dep A Dep A Dep B Dep B Dep B Dep B Dep B Dep B Dep C Dep C Dep C Dep C Dep C Dep C Dep D Dep D Dep D Dep D Dep D Dep D Profile Setting Policy Notification Login out Employees
- 21. Screenshots
- 22. Customer, Employee, Supplier Head Manager IT Dep HR Employee Employee Employee Employee Dep A Dep B Dep C Dep D Suppliers General Dep Customer
- 23. Security • Each Member will get unique Username & Password • Information for customer is allowed only for customer • Information for employees only allowed for employee. • Information for suppliers only allowed for suppliers. • The roles will be setup for each department • Polices will be written and published in each section in portal.
- 24. Security
- 25. Security
- 26. Some API List • REST API • SOAP API • Chatter REST API • Bulk API • Metadata API • Streaming API • Apex REST API • Apex SOAP API • Tooling API
- 27. REST API • Helps to get access into object. • It uses a protocol called REST. • It uses a Synchronous connection. • Data Format is JSON, XML • It works best with Mobile Devices. • Useful with Browser. • Useful with social application. • It enhance the collaboration among the company.
- 28. SOAP API • SOAP is web based web services • Uses SOAP protocol. • Data Format is XML • It uses a Synchronous connection. • It helps to create, retrieve, update , or delete data. • Good for web search. • Used mostly in business environment. • Example for our Company is ERP which SOAP used.
- 29. Chatter API • Allows Group Gathering, such as social media. • Uses REST protocol. • Format JSON , XML • It uses Synchronous (photos are processed asynchronously) communication • It uses a Synchronous connection. • It interacts with many application. • Mobile active. • It allows a programmatic access to the Chatter. • used to enhance the collaboration inside the community.
- 30. Metadata API • It helps developer regarding customization. • Management of the Metadata model. • Uses the XML data format. • Uses SOAP/WSDL protocol. • It uses an asynchronous connection. • Used for retrieve, deploy, create, update, or delete. • Help to migrate changes from sandbox environment to production.
- 31. Streaming API • Provides the data change capability. • Uses Bayeux protocol. • Data Format is JSON. • It uses Asynchronous (stream of data) connection. • It is used to send notification for any update. • Improve performance. • Reduces API calls.
- 32. Apex REST API • Allows building own REST API. • Uses XML, JSON, CUSTOM data format. • It uses a Synchronous connection. • You need build custom JSON responses. • Uses REST protocol. • Helps to interact with out side source. • OAuth 2.0 and Session ID for authorization accepted. • Enhance the connection to our side application.
- 33. APEX SOAP API • Allows to create different SOAP API. • Uses XML data format. • Require WSDL(Web Services Description Language). • Need to build custom XML responses. • It uses a Synchronous connection. • Uses SOAP/WSDL protocol. • Helps to interact with out side source. • OAuth 2.0 and Session ID for authorization accepted. • Enhance the connection to our side application.
- 34. Tooling API • Allows developer to build tools for force.com application. • Uses REST and SOAP protocol. • JSON, XML, Custom data format. • It uses an asynchronous connection. • Used to mange and deploy APEX classes. • Helps to manage and deploy components, triggers and Visualforce pages . • set checkpoints or heap dump markers, execute anonymous Apex, and access logging and code coverage information.
- 35. Waterfall Approaches “The waterfall model is a model which was developed for software development; that is to create software. It is called as such because the model develops systematically from one phase to other in a downward fashion, like a waterfall.” http://www.waterfall-model.com/
- 36. Waterfall Models “• Definition Study/Analysis • Basic Design • Technical Design/Detailed Design • Construction • Testing • Integration • Management and • Maintenance.” http://www.waterfall-model.com/
- 37. Waterfall • Collecting ideas and analyzing • Duration one month • The basic design of the software will be created using tools such MS, Photoshop and ect.. • Duration 3 weeks and 1 week discussion. • The Objects and the components of the design will be placed. • Functions will be decided • Duration 3 weeks
- 38. Waterfall Approaches • Putting the components and functions together. • Coding will be done • Duration of this will be the 6 weeks • Testing of the portal begins. • Each system sections will be tested. • Duration will be 3 weeks • System will be deployed • Maintenance & Management of the system to assure the liefetime.
- 39. Carl Sagan “Somewhere, something incredible is waiting to be known.”
- 40. From Redar Ismail Thank you so much for every one Hope you guys a wonderful and peaceful holiday.
- 41. Screenshots
- 42. Screenshots
- 43. Screenshots
- 44. Screenshots
- 45. Screenshots
- 46. Screen Shots
- 47. Screenshots
- 48. Screenshots
- 49. Screenshots
- 50. Screenshots
- 51. Screenshots
- 52. Screenshots
- 53. ScreenShots
- 54. Screenshots
- 55. Screenshot