Knowledge Sharing

Right balance of technical skills and personalities, and organizing that group so that the members work together effectively. Personality Type Task-oriented - The motivation for doing the work is the work itself. who are motivated by the intellectual challenge of software development. Self-oriented - Who are principally motivated by personal success and recognition. They are interested in software development as a means of achieving their own goals. Have longer-term goals, such as career progression, that motivate them and they wish to be successful in their work to help realize these goals. Interaction oriented - The principal motivation is the presence and actions of co-workers. People go to work because they like to go to work. Most software engineering is a group activity The development schedule for most non-trivial software projects is such that they cannot be completed by o...

The Stakeholders Senior manager – define business issues. Project (technical) manager – plan, motive, organize and control practitioners. Practitioners – deliver technical skill. Customers – specify the requirements. End user – directly interact with product. Team Leaders MOI Model of Leadership M otivation - The ability to encourage (by push or pull) technical people to produce to their best ability. O rganization - The ability to mold exiting processes that will enable the initial concept to be translated into a final product. I deas or innovation - The ability to encourage people to create and feel creativity People Need Hierarchy Characteristics of Team Leaders Problem solving Ability of diagnose the technical and organizational issues Systematically structured solution or motivate practitioners to develop the solution Apply lessons learned from past projects Managerial Identity Take responsibility of a assigned project Mus...

Projects need to be managed because professional software engineering is always subject to organizational budget and schedule constraints. The project manager’s job is to ensure that the software project meets and overcomes these constraints as well as delivering high-quality software. Important goals are: Deliver the software to the customer at the agreed time. Keep overall costs within budget. Deliver software that meets the customer’s expectations. Maintain a happy and well-functioning development team. Project Management Spectrum People Managing People Teamwork Product Process Project

The class diagram is a static diagram. It represents the static view of an application.Class diagram is not only used for visualizing, describing and documenting different aspects of a system but also for constructing executable code of the software application. The class diagram describes the attributes and operations of a class. The UML diagrams like activity diagram, sequence diagram can only give the sequence flow of the application but class diagram is a bit different. So it is the most popular UML diagram in the coder community. So the purpose of the class diagram can be summarized as: Analysis and design of the static view of an application. Describe responsibilities of a system. Base for component and deployment diagrams. Forward and reverse engineering. Identifying Analysis Classes From a System: General classifications for a potential class External entity (e.g., another system, a device, a person) Thing (e.g., report, screen display) Occurrence or...

Allows the modeler to represent the flow of activities described by the use-case and at the same time indicate which actor (if there are multiple actors involved in a specific use-case) or analysis class has responsibility for the action described by an activity rectangle. A swim lane diagram, sometimes called a cross-functional diagram. It is a process flowchart that provides richer information on who does what . It can also be expanded to show times— when tasks are done and how long they take. Example :Swim lane Diagram for POS Swim lane Diagram for POS

Activity Diagram Tools: Activity Diagram Tools Synchronization Bar: A Synchronization Bar is used to describe an intermediary step in a process in an activity diagram.  This intermediary process re-establishes a logical level, usually the result of several inputs. Example :Activity Diagram for Log in System Activity Diagram for Log in System

It is effective to use the first person “I” to describe how the actor interacts with the software. Format of the text part of a use case. Example Use-case title : Use-case text for system user. Actor : system user. Description : I can add new member in this system also i can add a subject... ... ... ... ... ... ...  

Elements of the Analysis Model 1. Scenario Based Element Use case Diagram Use-cases Text Activity Diagrams Swim Lane Diagrams 2. Class Based Element Class Diagram Analysis Packages CRC Models Collaboration Diagrams 3. Flow Oriented elements Data Flow Diagram Control Flow Diagrams Processing Narratives 4. Behavioral elements State Diagrams Sequence Diagrams I will discuses all things one by one

Software analyses are dividing into five parts: Analysis Modelling Project Management Project planning and Scheduling Project Estimation Quality Management Objectives of analysis model To describe what the customer require. To establish a basis for the creation of a software design. To define a set of requirements that can be validated once the software is built What is a model? Ans:a model is a simplification of reality Why do we model? -we build models so that we can better understand the system we are developing. -we build models of complex systems because we cannot comprehend such a system in its entirety. -four aims to achieve:- 1. help us to visualize a system. 2. permit us to specify the structure/behavior of a system. 3. give us a template that guides us in constructing systems. 4.document the decisions we have made.