This is website for campus to share data between students and teachers, like, notes, queries,etc.

1. WEEKLY PRESENTATION NO. 1
ONLINE SOCIAL
NETWORK
ViMEET ACES [ ASSOCIATION OF COMPUTER ENGG. ]

2. Introduction
 Attempts to make social networking sites began in the early 90s
 Some of the first popular sites were classmates.com (1995) and sixdegrees.com (19
97)
 Today, there are hundreds of social networking sites, ranging from dating sites to the
friendship based sites, such as Facebook and Myspace

3. Popular Social Networking Sites

4. Benefits of Social Networking Sites
 Social networking sites are easily accessible
 Helps encourage communication and keep people connected
 Improve communication skills
 Users learn basic and some advanced technological skills

5. Questions:
Q: Why PHP ?
Ans: Easy to understand, can be hosted anywhere, cross platform,
Easy to deploy and nice presentation.
Q: How HTML and CSS will benefits ?
Ans: HTML - Easy to code, easy to understand errors, it can embedded
with CSS and JavaScript.
CSS – It allows you to style the web page.

6. Questions:
Q: How JavaScript is useful ?
Ans: It is a programming language used in web pages. JavaScript is the language that makes the web
pages more dynamic. JavaScript is practically used by every website. It is used in client-side
Scripting.
Q: Idea about client and server side scripting ?
Ans: Server-side scripting is a technique used in web development which involves employing
scripts on a web server which produce a response customized for each user's (client's) request
to the website. Server-side scripting is distinguished from client-side where embedded scripts,
such as JavaScript, are run client-side in a web browser, but both techniques are often used
together.

7. Questions:
Q: Which programming approach is better ?
Ans: Object-oriented programming is suitable for large project and long term maintenanc
e of software of web projects, this method of programming poses its own disadvantages
as object-oriented programming tends to be more complex than structured programming
as there is a lot as far as design the decisions that need to be made and consequently th
e entire task of managing the project may be a bit difficult to the inexperienced web devel
oper.

8. SDLC:
Fig no: 1 SDLC
SDLC is nothing but a Software Development Life Cycle. It is a process followed for a software
project within a software organization. The life cycle defines a methodology for improving the q
uality of software and the overall development process.

9. Zachman framework:
• The Zachman Framework is an enterprise ontology and is a funda
mental structure for Enterprise Architecture which provides a formal
and structured way of viewing and defining an enterprise.
• The first are primitive perspectives : What, How, When, Who, Wher
e, and Why.
• The second is derived from the philosophical concept of reification, t
he transformation of an abstract idea into an instantiation.
• The framework defines how perspectives are related according to c
ertain rules or abstractions.

10. • Framework set of rules:
• Rule 1 :The columns have no order
• Rule 2 :Each column has a simple generic model
• Rule 3 :The basic model of each column must be unique
• Rule 4 :Each row describes a distinct, unique perspective
• Rule 5 :Each cell is unique
• Rule 6:The logic is recursive
• Rule 7 :The composite or integration of all cell models in one row co
nstitutes a complete model from the perspective of that row

12. ER Diagram:

13. DFD:
A Data Flow Diagram (DFD) is a graphical representation of the "flow" of data through a
n information system, modelling its process aspects. A DFD is often used as a preliminary
step to create an overview of the system, which can later be elaborated. DFDs can also b
e used for the visualization of data processing (structured design).
TYPES OF DFD
A Physical DFD shows how the system is actually implemented, either at the moment, or
how the designer intends it to be in the future.
A Logical DFD attempts to capture the data flow aspects of a system in a form that h
as neither redundancy nor duplication.

14. DFD:
Data Flow Diagram : Context level

15. DFD:
Level 1 DFD :

16. DFD:
Level2 : Account Level2 : Post articles

17. DFD:
Level2 : Services

18. DFD:
Level3 : services/notify Level3 : services/chat

19. DFD:
Level3 : services/settings

20. Risk Management
1. Identify: Search for the risk before it creates major use.
2. Analyze: Understand nature, kind of risk and info about
the risk.
3. Plan: Convert them into action and implement them.
4. Track: We need to monitor necessary actions.
5. Control: Correct the deviation and make any necessary
amendments
6. Communicate: Discuss about the emerging risks and th
e current risks and the plans to be taken
week 1

21. Risk Management
• Social network enables you to engage customers in real time, add s
ales channels, and enhance your brand and market research.
• However, you need to be aware of and prepared for the risks that so
cial media can bring. These risks include employees leaking confide
ntial information or intellectual property (either inadvertently or on pu
rpose), which can result in reputational issues as well as the potenti
al for legal and regulatory challenges.
• Many organisations are struggling to develop and maintain a clear-c
ut social media governance framework as a central part of their soci
al media strategy.
week 1

22. Use Case Diagram:

23. Class Diagram:
• Class diagrams gives the static design view of system
• A class diagram shows a set of classes and their relationships
Contents:
• Classes
• Relationships
1. Association
2. Aggregation
3. Generalization
4. Composition

24. Class Diagram:

25. Activity Diagrams:
• Activity diagram is basically a flow chart to represent the flow of
control from one activity to another activity .
• It emphasize the flow of control
Content:
• Activity states or action states
• Transitions
• Branching
• Forking and joining
• Objects

26. Activity Diagrams:

27. Sequence Diagram:
• Sequence diagram shows the interaction between the classes in ter
ms of exchange of messages over time
• They are also called as event diagrams

28. Sequence diagram:
• Components :

29. Sequence Diagram:

30. Component Diagram:
• A component diagram shows the organization and dependencies
among the a set of component
• Component diagrams are use to model the static implementation
view of a system
• Component diagrams the are essentially class diagrams that focus
on a system components

31. Component Diagram:

32. Deployment Diagram:
• Deployment diagrams are used to visualize the topology of the physical
components of a system where the software components are deployed.
• So deployment diagrams are used to describe the static deployment vie
w of a system. Deployment diagrams consist of nodes and their relation
ships.
• Deployment diagrams are used for describing the hardware compon
ents where software components are deployed.Component diagrams
and deployment diagrams are closely related.

33. Deployment Diagram:

34. First Page: