“Associate Software Engineer Frequently Asked Questions by expert members with experience in Associate Software Engineer. These questions and answers will help you strengthen your technical skills, prepare for the new job test and quickly revise the concepts”
A software cycle deals with various parts and phases from planning to testing and deploying. All these activities are carried out in different ways, as per the needs. Each way is known as a Software Development Lifecycle Model (SDLC).
Some SDLC models
★ The Linear model (Waterfall)
- Separate and distinct phases of specification and development
- All activities in linear fashion
- Next phase starts only when first one is complete
* Evolutionary development
- Specification and development are interleaved (Spiral,incremental,prototype based,Rapid Application development)
- Incremental Model (Waterfall in iteration)
- RAD(Rapid Application Development) - Focus is on developing quality product in less time
- Spiral Model - We start from smaller module and keeps on building it like a spiral. It is also called Component based development.
★ Formal systems development
- A mathematical system model is formally transformed to an implementation
★ Agile Methods
- Inducing flexibility into development
★ Reuse-based development
- The system is assembled from existing components
Collaboration Diagrams:
An alternative presentation of a sequence diagram. We uses boxes to desibe objects, the lines connecting two boxes indiate that the objects collborate with to one another and we use a multiplicity factor "*" to indiate that all elements of the aggregation receive a message.
Package Diagram:
Complete set of sequence Diagrams or Collaboration Diagrams of the system.
Design Patterns are simple and elegant solutions of commonly occuring problems in software design. Design Patterns make it easier to reuse successful designs and architectures of expereinced and Professional Designers.
There are three types of Patterns -
1) Creational - Concerned with creation of objects
2) Structural - Concerned with composition of classes or objects
3) Behavioral - characterize the ways in which classes and objects interact and distribute responsibility.
Sequence Diagrams are pictorial representation of event happening according to the time line. In sequence Diagrams, we show respective class names by a small box and the event as a arrow.
Sequence Diagrams help in describing the normal course and alternative course of use cases.
An architecture expresses a fundamental structural organization schema for software systems. It provides a set of predefined subsystems, specifies their responsibilities, and includes rules and guidelines for organizing the relationships between them.
★ Object-Oriented/Abstract Data Style
★ Layered Hierarchies
★ Blackboard architecture
★ involving shared access to data with loosely coupled agents
★ Client/Server
★ Three tier Client/Server architectures
★ Peer-to-Peer Architecture
Use cases are graphical represenation of system parts and there interaction that is taking place. Normally we depict
the part of the systems who are involved in some activity as actors.
Class Diagrams are a part of designing proess. After coming up with use cases of the system, we take each use case and come up with the
classes that we need to perform that functionality. Each class will have Class Name, Attribues and Operations associate with it.
Some of the features of the classes are -
- Each class should have well defined responsibilities
- These responsibilities should be cohesive i.e. the system as a whole looks sensible and looks together.
Any previous programming experience that you may have is certainly an asset, but it is not a requirement. It is a very common myth that SE is mainly programming. In fact, SE programs put a lot more emphasis on software development practice and process, including advanced areas of software architecture, requirements management, quality assurance and process improvement.
On more than one occasion, when I gave a star candidate a coding question, he zeroed in on the most optimally performant solution, identified the boundary cases, and began writing well-designed code. Midway through the problem, he makes a little error -- getting the order of operations wrong on the first try, or having an off-by-1 error, or forgetting to declare a variable.
When I point it out, the candidate responds with horror and then becomes so nervous that it impacts his performance during the rest of the interview.
The fear is unfounded. An awesome candidate making a little error is like a concert violinist playing a challenging Brahms concerto and hitting two wrong notes. Sure, the audience could tell that he made mistakes, but they don't get confused as to whether he's actually at Twinkle-Twinkle-Little-Star level.
Even if you completely bomb one question, many interviewers ask you multiple questions and will forgive a single mishap. Even bombing an entire interview is recoverable if the other interviews go well.
PSP stands for Personal Software Process.
★ PSP Objectives are -
- To introduce individuals to a process-based approach to developing software
- To show individuals how to measure, estimate, schedule, and track their work
- To show individuals how to improve the quality of their programs
- In general PSP improves quality and productivity
- The time saved in testing because of better quality reduces time across the project by 20-40%
Object Oriented Design Tools - Rational Rose, Rhapsody, Telelogic Tau G2
UI Design Tools - Rapid/Paper prototypes, Simple
SUMI (Software Usability Measurement Inventory ) - It will tell you how your product compares to this standardization base: whether you are about average for the market, below, or above.
Computer systems are pervasive and have a major impact on society. Software is a critical component of all computer systems, including the "embedded systems" used in communication networks, vehicles, consumer electronics and medical devices. Software engineers have the knowledge and skills needed to produce high-quality, effective software on which all these computer systems depend.
Advantage of PSP:
- To manage your work & assess/build your talents/skills
- To plan better
- To track your performance precisely
- To measure the quality of your software products
While computer engineering programs include courses in software, SE programs incorporate much more detail in software development practice and process, including advanced areas of software architecture, requirements management, quality assurance, and process improvement. Software engineering programs do not stress computer hardware and electronics as much as computer engineering programs do.
On the other hand, software engineering is based on computer science, as other engineering disciplines are based on natural or life sciences. However, software engineering adds an emphasis on issues of process, design, measurement, analysis and verification. In general, scientists seek new knowledge, while engineers want to build things, solve problems, and help people. Both roles are important.
Software Engineering is all about using engineering principles for the production of software. If you like computers, like solving challenging problems and would like to make an impact on the world in which we all live, you should consider software engineering (SE).
Computer systems are an integral part of today's society. Software is a critical component of all computer systems, including the "embedded systems" used in communication networks, vehicles, consumer electronics, and medical devices. Software engineers have the knowledge and skills needed to produce high-quality, effective software on which all these computer systems depend.
BSSE program is one of the first four ABET accredited programs in the United States. Our curriculum provides a strong foundation upon which to build a successful SE career.
It is used in verifying software restart capabilities after a "disaster".
Some Features of RUP are -
★ Online Repository of Process Information and Description
★ Templates for all major artifacts, including:
- Requirements tracking (RequisitePro templates)
- Use Cases (Word Templates )
- Project Management (Project Templates)
★ Process Manuals describing key processes
Probably one term which you must be aware of as we often hears this software is in Alpha phase and in Beta phase. Here Testing is done by representative set of potential users for trial use. Please Note - in-house (alpha testing) - external (beta testing).
Regression Testing accdoing to IEEE is "selective retesting of a system or component to verify that modifications have not caused unintended effects". It is repetition of tests intended to show that the software's behavior is unchanged, except insofar as required. It Can be done at each test level.
IEEE Defines it as The process of testing an integrated hardware and software system to verify that the system meets its specified requirements. It is tested against system specification. May test manual procedures, restart and recovery, user interface, stress, performance. In System Testing, real data is used and sometimes users participations is also used.
rendc.org
Whether it is technological solutions or user-oriented innovations, We have put together for you the best sources of HR Interview Questions and Answers, Tech Ideas, and Programming Tutorials."
Get all the latest information on rendc.org
© 2022 | All rights reserved.
RENDC
welcome to www.rendc.org
