Knowledge Sharing

 My Upwebhosting review Upwebhosting.com - Fraud Generally I am not in habit of posting such reviews but I don't want others to get fooled by the fake claims of upwebhosting.com so here is my upwebhosting review. They have named themselves as upwebhosting.com but in actual they should be named as downwebhosting.com My site is down from past 1 week. In-fact not just mine but sites of all other customers are down too from past 1 week. Upwebhosting site was also down but is up now but my site is still down. I have submitted serveral support tickets but never received any reply. Today I found that I am not even unable to login to billing area. Perhaps this guy has closed the account. Their facebook page is also full of such complaints. They have thousands of fake facebook likes on their page. After some digging I found that upwebhosting also owns nexgenz.com (Nexgenz Technologies) and the owner of both sems to be a Pakistani named Wajahat Ali. Hear I give give all my activities at

Below, you'll find a list of the most common IP commands for Windows and DOS. These include ipconfig, trace route, netstat, arp, route, hostname, control netconnections, and other popular DOS and Windows IP commands. Display Connection Configuration:  ipconfig /all Display DNS Cache Info:  ipconfig /displaydns Flush and Reset DNS Cache:  ipconfig /flushdns Release All IP Address Connections:  ipconfig /release Renew All IP Address Connections:  ipconfig /renew Re-Register the DNS connections:  ipconfig /registerdns Change/Modify DHCP Class ID:  ipconfig /setclassid Network Connections:  control netconnections Network Setup Wizard:  netsetup.cpl Test Connectivity:  ping domainname.com Trace Route:  tracert www.domainname.com Displays the TCP/IP protocol sessions:  netstat Display Local Route:  route Display Resolved MAC Addresses:  arp Display Name of Computer Currently on:  hostname Display DHCP Class Information:  ipconfig /showclassid NameServer Lookup:  nslookup domainname.com *

Download ja nex Templates Free

Due to the popularity of my previous post that guides how to  increase upload_max_filesize  on cPanel server I decided to create a more general article, that covers changing of other PHP settings using  php.ini  and .htaccess  files. In this article we will change the following php settings: memory_limit  – maximum amount of physical memory that can be allocated to PHP script max_post_size  – maximum size of data that can be transferred via POST method register_globals  – this variable allows to enable or disable register_globals file_uploads  – enables or disables file_uploads First we will create our  custom php.ini  file: Login to your cPanel account, open public_html directory and create blank php.ini file Put php settings that you would like to change into the file. I will put all php variables, but if you would like to leave default values for some of them you can exclude them from the list [PHP] ; increase php memory_limit to 128M memory_limit = 128M ; increase php max_post_size

Tablet and Mobile (as default): support 2 modes, portrait and landscape. Support 5 layouts (Extra-wide, wide, normal, tablet, mobile) Multiple module styles and badges styles to choose from Joomla 2.5.x compatible Cross Browser Support: IE7+, Firefox 2+, Safari 3+, Chrome 8+, Opera 9+ and other Standards-Supporting Browsers. Supports all mobile browsers Valid 508 Accessibility Well-commented css files flexible customization Demo Link:  Ja-mendozite-demo Download Link:  Ja-mendozite-download

MAC-Address is the hardware Network Address for the NIC which is unique for the system. However, there may be time when you need to change the MAC-Address for administrative purpose on a network. Some of the device drivers come with an option to change it from the device properties but not all (like my Broadcom Gigabit Ethernet Driver). For those who do not have the luxury of changing the MAC-Address from the device properties there is a way to do this  by editing the Windows Registry. To change MAC-Address for a Network card in Windows Registry: 1. Click Start – Run, type “regedit” 2. Navigate to [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318] HKEY_LOCAL_MACHINE     \SYSTEM         \CurrentControlSet             \Control                \Class                   \{4D36E972-E325-11CE-BFC1-08002BE10318}                 3. Under this key, you shoud see numbers in sequence as “0000″, “0001″ and so on. Click on one at a time to

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 Must be

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.

Use Case Diagrams: A use case in software engineering and systems engineering is a description of a system’s behavior. In other words, a use case describes "who" can do "what" with the system in question. The use case technique is used to capture a system's behavioral requirements by detailing scenario-driven threads through the functional requirements.  Actor: An actor represents a set of roles that users of use case play when interacting with these use cases. Actors can be human or automated systems. Actors are entities which require help from the system to perform their task or are needed to execute the system’s functions. Use Case Diagram for School Management Fig: Use Case Diagram for School Management Use Case Diagram for Point of Sale Fig: Use Case Diagram for Point of Sale

Traceability Tables Features traceability table: Shows how requirements relate to important customer observable system/product features. Source traceability table: Identifies the source of each requirement. Dependency traceability table: Indicates how requirements are related to one another. Subsystem traceability table: Categorizes requirements by the subsystem(s) that they govern. Interface traceability table: Shows how requirements related to both internal and external system interfaces.

Inception:  define scope and nature  How does a software project will started  Define business plan Identify breath and depth of market Rough feasibility analysis Identify working description Elicitation: help customer to define what is required Time to come out Problem of scope Boundary, avoid unnecessary technical details Problem of understanding Not sure about need Problem of volatility Requirement changing Elaboration: basic requirements are found and modified Inception and elicitation expanded and refined It is analysis modeling action Relationship and collaboration between classes are identified and generate use case diagram Negotiation: priorities, what is essential, what is required to maintain –defined Ahead to analysis Cost estimation, delivery time, elimination - combination – modification of requirements Specification: problems are specified Written document Set of graphical or mathematical model Collection of scenario Prototype of combination of these Validation: cus

These define system properties and constraints e.g. reliability, response time and storage requirements. Constraints are I/O device capability, system representations, etc. i.e. Deactivate or delete record after 24 hrs Process requirements may also be specified mandating a particular programming language or development method. Non-functional requirements may be more critical than functional requirements. If these are not met, the system may be useless. Types of Nonfunctional requirement Product requirement: Examples The MHC-PMS shall be available to all clinics during normal working hours (Mon–Fri, 0830–17.30). Downtime within normal working hours shall not exceed five seconds in any one day. Organizational requirement:  Examples Users of the MHC-PMS system shall authenticate themselves using their health authority identity card. External requirement:  Examples The system shall implement patient privacy. Non-functional requirements implementation Non-functional requirements may affec

Describe functionality or system services. Depend on the type of software, expected users and the type of system where the software is used. Functional user requirements may be high-level statements of what the system should do. Functional system requirements should describe the system services in detail. Examples: Functional requirements for the MHC-PMS A user shall be able to search the appointments lists for all clinics. The system shall generate each day, for each clinic, a list of patients who are expected to attend appointments that day. Each staff member using the system shall be uniquely identified by his or her 8-digit employee number. Requirements imprecision Problems arise when requirements are not precisely stated. Ambiguous requirements may be interpreted in different ways by developers and users. Consider the term ‘search’ in requirement 1 User intention – search for a patient name across all appointments in all clinics; Developer interpretation – search for a patient nam

User requirements Statements in natural language plus diagrams of the services the system provides and its operational constraints. Written for customers. System requirements A structured document setting out detailed descriptions of the system’s functions, services and operational constraints. Defines what should be implemented so may be part of a contract between client and contractor. Functional requirements Statements of services the system should provide, how the system should react to particular inputs and how the system should behave in particular situations. May state what the system should not do. Non-functional requirements Constraints on the services or functions offered by the system such as timing constraints, constraints on the development process, standards, etc. Often apply to the system as a whole rather than individual features or services.

What is Requirement? Ans: It may range from a high-level abstract statement of a service or of a system constraint to a detailed mathematical functional specification. Its Begin from Communication and continues into the modelling. What is Requirement Engineering? The process of establishing the services that the customer requires from a system and the constraintunder which it operates and is developed. Requirement reflects the needs of customer for a system that serves a certain purpose such as controlling a device, placing an command or finding information. The process of finding out, analyzing, documenting and checking these services and constrains is called requirement engineering (RE). Bridge to design and construction. Example of Types of Requirement

Testing Principles All tests should be traceable to customer requirements Tests should be planned long before testing begins Testing should begin “in the small” and progress toward testing “in the large” Deployment Principles Customer expectation for the software must be managed A complete delivery package should be assembled and tested A support government must be established before the software is delivered Appropriate instructional materials must be provide to end user Buggy software should be fixed first, delivered later

Preparation : Before writing code Understand the problem you’re trying to solve Understand basic design principles and concepts Pick a programming language that meets the need s of the software to be built and the environment in which it will operate Create a set of unit tests that will be applied once the coding is complete for each component Coding: When writing code Constrain your algorithm by following structured programming practice Select the data structure that will meet the needs of design Understand the software architecture and create interfaces that are consistent with it Select meaningful variable name Create visual layout

Analysis Modelling Principles The information domain of a problem must be represented The functions that the software performs must be defined The behaviour of the software must be represented The models that depict information, function and behaviour must be partitioned is a manner that uncovers detail a layered or hierarchical fashion The analysis task should move from essential information toward implementation detail Design Modelling Principles Design should be traceable to the analysis model Always consider the architecture of the system to be built Design of data is as important as design of processing functions Interface must be designed with care Component level design should be functionally independent Design representation should be easily understandable The design should be developed iteratively. With each iteration, the designer should strive for greater simplicity

Understand the scope of the project Involve the customer in the planning activities Recognize that planning is iterative Estimate based on what you know Consider risk as you define the plan Be realistic Define how you intend to ensure quality Track the plan frequently and make adjustment as required

Understand the problem ( communication and analysis) Plan a solution (modelling and software design) Carry out the plan (code generation) Examine the result for accuracy (testing and quality assurance) Core principles for Software Engineering : The reason it all exists KISS! (Keep It Simple Stupid) Maintain the vision Be open to the future Plan ahead for reuse Think!

Main Business Communication principles Business communication is the communication between the people in the organization for the purpose of carrying out the business activities. A business can flourish when all objectives of the organization are achieved effectively . For efficiency in an organization, all the people of the organization must be able to convey their message properly . The exchange of ideas and understanding within and outside the organization to achieve the business goals is known as business communication. Communication Skills Needed in Business Speaking well Writing well Displaying proper etiquette (manners) Listening attentively The Basic Forms Of Communication Nonverbal communication: Facial Gesture Vocal characteristic Personal appearance Touching behavior Use time and space Verbal Communication: speaking and writing Listening and Reading   Why Business Needs to Communicate? Communication is vital to every part of business. Example for Emp

1.What is software? Ans:Computer programs and associated documentation. Software products may be developed for a particular customer or may be developed for a general market. 2.What is software engineering? Ans:Software engineering is an engineering discipline that is concerned with all aspects of software production. 3.What is the difference between software engineering and system engineering? Ans:System engineering is concerned with all aspects of computer-based systems development including hardware, software and process engineering. Software engineering is part of this more general process 4.What are the key challenges facing software engineering? Ans:Coping with increasing diversity, demands for reduced delivery times and developing trustworthy software. 5.What are the costs of software engineering? Ans:Roughly 60% of software costs are development costs, 40% are testing costs. For custom software, evolution costs often exceed development costs. 6.What are the best software engine

Rational Unified Process: The Rational Unified Process (RUP) is an iterative software development process framework created by the Rational Software Corporation, a division of IBM since 2003. RUP is not a single concrete prescriptive process, but rather an adaptable process framework, intended to be tailored by the development organizations and software project teams that will select the elements of the process that are appropriate for their needs. RUP is a specific implementation of the Unified Process. •Inception The primary objective is to scope the system adequately as a basis for validating initial costing and budgets. In this phase the business case which includes business context, success factors (expected revenue, market recognition, etc.), and financial forecast is established. To complement the business case, a basic use case model, project plan, initial risk assessment and project description (the core project requirements, constraints and key features) are generated. After

Spiral model: The spiral model is a software development process combining elements of both design and prototyping-in-stages, in an effort to combine advantages of top-down and bottom-up concepts. Also known as the spiral life-cycle model (or spiral development), it is a systems development method (SDM) used in information technology (IT). This model of development combines the features of the prototyping and the waterfall model. The spiral model is intended for large, expensive and complicated projects.   History: The spiral model was defined by Barry Boehm in his 1986 article "A Spiral Model of Software Development and Enhancement". This model was not the first model to discuss iterative development. As originally envisioned, the iterations were typically 6 months to 2 years long. Each phase starts with a design goal and ends with the client (who may be internal) reviewing the progress thus far. Analysis and engineering efforts are applied at each phase of the project, wit

RAD, or rapid application development, is an object-oriented approach to systems development that includes a method of development as well as software tools •RAD is used when –The team includes programmers and analysts who are experienced with it. –Users are sophisticated and highly engaged with the goals of the company. •Negative Aspect - RAD is based on Object Oriented approach. - If commitment is lacking RAD will fail. - RAD is not appropriate when technical risks are high, e.g. this occurs when a new application makes heavy use of new technology. You can also view: 1. Boehms Spiral Process Model 2. Rational Unified Process Model 3. Rapid Application Development-RAD 4. Prototyping Process Model 5. Incremental Process Model 6. Component Based Software Engineering 7. Evolutionary Process Development Model 8. Waterfall Process Model 9. Software Process Framework Activity

•Gather requirements •Quick design focusing on what will be visible to user – input & output formats •Process iterated until customer & developer satisfied – then throw away prototype and rebuild system to high quality. - Insufficient analysis. - Excessive development time of the prototype. - High expectations for productivity with insufficient effort. You can also view: 1. Boehms Spiral Process Model 2. Rational Unified Process Model 3. Rapid Application Development-RAD 4. Prototyping Process Model 5. Incremental Process Model 6. Component Based Software Engineering 7. Evolutionary Process Development Model 8. Waterfall Process Model 9. Software Process Framework Activity

•Main characteristics –Hybrid model that combines elements of the waterfall and evolutionary paradigms. –The specification, design, and implementation phases are broken in smaller increments. •Advantages –Provides better support for process iteration. –Reduces rework in the software construction process. –Allows early delivery of parts of the system. –Supports easier integration of sub-systems. –Lower risk of project failure. –Delivery priorities can be more easily set. •Disadvantages –Mapping requirements to increments may not be easy. –Common software facilities may be difficult to identify. –Some decisions on requirements may be delayed. •Applicability: –When it is possible to deliver the system “part-by-part” . You can also view: 1. Boehms Spiral Process Model 2. Rational Unified Process Model 3. Rapid Application Development-RAD 4. Prototyping Process Model 5. Incremental Process Model 6. Component Based Software Engineering 7. Evolutionary Process Development Model 8. Water

•Main characteristics –Makes intensive use of existing reusable components. –The focus is on integrating the components rather than on creating them from the scratch. •Advantages –Reduces considerably the software to be developed “in-house”. –Allows faster delivery. –In principle, more reliable systems, due to using previously tested components. •Disadvantages –agreement in requirements are needed. –Less control over the system’s evolution •Applicability: –When there is a pool of existing components that could satisfy the requirements of the new product. –Emerging trend: integration of web services from a range of suppliers. You can also view: 1. Boehms Spiral Process Model 2. Rational Unified Process Model 3. Rapid Application Development-RAD 4. Prototyping Process Model 5. Incremental Process Model 6. Component Based Software Engineering 7. Evolutionary Process Development Model 8. Waterfall Process Model 9. Software Process Framework Activity