Chuyển đến nội dung chính

How to make a software company ?

from $ Making an app is one thing and making a software company is another different things. these are two different things. 

here is the answer to How to make a software company?


 mobile apps or software can be made without coding, there are so many tools available on the internet that provides you with a platform to develop your own idea and convert it into an app or software. but to start an app development company you will not only have to learn the multiple programming languages but their quality and management too. to learn these all you will have to learn the b.tech with computer science or information technology and MBA for management. one more thing online videos or article can't replace this thing. but if you don't want to do this then there is a shortcut for you.

you can do a short-term course on the following topics. either with only one large program or may of short programs. but the objective is to cover the following topics.

Course Structure
The course is structured in a way that it covers all the aspects of software engineering required for better understanding of the students.

B. Tech Software Engineering provides students knowledge of evaluating the right codes and software for specific tasks.

Outlines
: The Scope of Software Engineering

2: Software Life-Cycle Models

3: The Software Process

4: Development Teams

5: Software Engineering Tools

6: Testing

7: From Modules to Objects

8: Reusability and Portability

9: Planning and Estimating

10: Requirements

11: Classical Analysis

12: Object-Oriented Analysis

13: Design14: Implementation

15: Post-delivery Maintenance

16: More on Unified Modeling Language (UML)

17: Emerging Technologies

Syllabus
It teaches the students all the necessary skills about software systems, application packages, and software making software.

Subjects that are included in the syllabus are added so that it builds an ability in students to be able to design a system that meets desired results within realistic constraints.

the topics covered in this course are: (topics are separated by comma )

Introduction: Introduction to Software Engineering, Software Components, Software Characteristics, Software Crisis, Software Engineering Processes, Similarity and Differences from Conventional Engineering Processes, Software Quality Attributes. Software Development Life Cycle (SDLC) Models: Water Fall Model, Prototype Model, Spiral Model, Evolutionary Development Models, Iterative Enhancement Models.

Software Requirement Specifications (SRS): Requirement Engineering Process: Elicitation, Analysis, Documentation, Review and Management of User Needs, Feasibility Study, Information Modelling, Data Flow Diagrams, Entity Relationship Diagrams, Decision Tables, SRS Document, IEEE Standards for SRS. Software Quality Assurance (SQA): Verification and Validation, SQA Plans, Software Quality Frameworks, ISO 9000 Models, SEI-CMM Model.

Software Design: Basic Concept of Software Design, Architectural Design, Low-Level Design: Modularization, Design Structure Charts, Pseudo Codes, Flow Charts, Coupling and Cohesion Measures, Design Strategies: Function Oriented Design, Object Oriented Design, Top-Down, and Bottom-Up Design. Software Measurement and Metrics: Various Size Oriented Measures: Halstead's Software Science, Function Point (FP) Based Measures, Cyclomatic Complexity Measures: Control Flow Graphs.

Software Testing: Testing Objectives, Unit Testing, Integration Testing, Acceptance Testing, Regression Testing, Testing for Functionality and Testing for Performance, TopDown and Bottom-Up Testing Strategies: Test Drivers and Test Stubs, Structural Testing (White Box Testing), Functional Testing (Black Box Testing), Test Data Suit Preparation, Alpha and Beta Testing of Products. Static Testing Strategies: Formal Technical Reviews (Peer Reviews), Walk Through, Code Inspection, Compliance with Design and Coding Standards.

Software Maintenance and Software Project Management: Software as an Evolutionary Entity, Need for Maintenance, Categories of Maintenance: Preventive, Corrective and Perfective Maintenance, Cost of Maintenance, Software Re-Engineering, Reverse Engineering. Software Configuration Management Activities, Change Control Process, Software Version Control, An Overview of CASE Tools. Estimation of Various Parameters such as Cost, Efforts, Schedule/Duration, Constructive Cost Models (COCOMO), Resource Allocation Models, Software Risk Analysis and Management.


REFRENCE BOOK

1. RS Pressman, Software Engineering: A Practitioners Approach, McGraw Hill. 2. Pankaj Jalote, Software Engineering, Wiley 3. Rajib Mall, Fundamentals of Software Engineering, PHI Publication. 4. KK Aggarwal and Yogesh Singh, Software Engineering, New Age International Publishers. 5. Ghezzi, M. Jarayeri, D. Manodrioli, Fundamentals of Software Engineering, PHI Publication. 6. Ian Sommerville, Software Engineering, Addison Wesley. 7. Kassem Saleh, “Software Engineering”, Cengage Learning. 8. P fleeger, Software Engineering, Macmillan Publication


Nhận xét

Popular Posts

Digital Finance Stakeholders

Digital forensic students looking to research digital finance may find this useful as a starting point. Through the financial support of the Bill & Melinda Gates Foundation, MicroSave isconducting a four-year research project in the following eight focus countries as part ofthe Agent Network Accelerator (ANA) Project: http://www.helix-institute.com/sites/default/files/Publications/161101%20ANA%

MSI wraps its newest mid-tower case in tinted tempered glass

This case will highlight (or expose) your cable management skills   As reported by PCGamer, MSI is rolling out a new Mag Pylon mid-tower case that it's positioning under its "Gaming Gear" umbrella of products. It has three tinted tempered glass panels—both sides and the front—to show off your build, and supports the company's Mystic Light Sync feature to synchronize lighting across other MSI products. The case comes with three 120mm RGB fans aligned in the front. You could swap them out for a pair of larger 140mm fans if you wanted to, and there is also room to install up to two 140mm or 120mm fans (or a liquid radiator and fans) in the top and a 120mm in rear. Cable management is a bit more important in a see-through case like this, unless you're a honey badger and just don't care what your build looks like. Assuming you do, you'll find four large cable cutouts to the right of the motherboard tray. There are also several cable tie downs on the back of th...