We found 33 results that contain "software engineering"

What is SDLC?
SDLC is a process followed for a software project, within a software organization. It consists of a detailed plan describing how to develop, maintain, replace and alter or enhance specific software. The life cycle defines a methodology for improving the quality of software and the overall development process.
The following figure is a graphical representation of the various stages of a typical SDLC.

A typical Software Development Life Cycle consists of the following stages −
Stage 1: Planning and Requirement Analysis
Requirement analysis is the most important and fundamental stage in SDLC. It is performed by the senior members of the team with inputs from the customer, the sales department, market surveys and domain experts in the industry. This information is then used to plan the basic project approach and to conduct product feasibility study in the economical, operational and technical areas.
Planning for the quality assurance requirements and identification of the risks associated with the project is also done in the planning stage. The outcome of the technical feasibility study is to define the various technical approaches that can be followed to implement the project successfully with minimum risks.
Stage 2: Defining Requirements
Once the requirement analysis is done the next step is to clearly define and document the product requirements and get them approved from the customer or the market analysts. This is done through an SRS (Software Requirement Specification) document which consists of all the product requirements to be designed and developed during the project life cycle.
Stage 3: Designing the Product Architecture
SRS is the reference for product architects to come out with the best architecture for the product to be developed. Based on the requirements specified in SRS, usually more than one design approach for the product architecture is proposed and documented in a DDS - Design Document Specification.
This DDS is reviewed by all the important stakeholders and based on various parameters as risk assessment, product robustness, design modularity, budget and time constraints, the best design approach is selected for the product.
A design approach clearly defines all the architectural modules of the product along with its communication and data flow representation with the external and third party modules (if any). The internal design of all the modules of the proposed architecture should be clearly defined with the minutest of the details in DDS.
Stage 4: Building or Developing the Product
In this stage of SDLC the actual development starts and the product is built. The programming code is generated as per DDS during this stage. If the design is performed in a detailed and organized manner, code generation can be accomplished without much hassle.
Developers must follow the coding guidelines defined by their organization and programming tools like compilers, interpreters, debuggers, etc. are used to generate the code. Different high level programming languages such as C, C++, Pascal, Java and PHP are used for coding. The programming language is chosen with respect to the type of software being developed.
Stage 5: Testing the Product
This stage is usually a subset of all the stages as in the modern SDLC models, the testing activities are mostly involved in all the stages of SDLC. However, this stage refers to the testing only stage of the product where product defects are reported, tracked, fixed and retested, until the product reaches the quality standards defined in the SRS.
Stage 6: Deployment in the Market and Maintenance
Once the product is tested and ready to be deployed it is released formally in the appropriate market. Sometimes product deployment happens in stages as per the business strategy of that organization. The product may first be released in a limited segment and tested in the real business environment (UAT- User acceptance testing).
Then based on the feedback, the product may be released as it is or with suggested enhancements in the targeting market segment. After the product is released in the market, its maintenance is done for the existing customer base.Video link:Embedded video link:Link: https://projects.invisionapp.com/d/main#/console/20294675/458743820/preview 

When project managing a distributed team in a variety of locations, a collaboration software (or project management) tool is an effective way to keep everyone on the same page and all of your project information in one place. However, using a great tool doesn’t magically make collaboration happen. Here are 10 best practices when using a collaboration software tool:

Share proactively - Assign team members to the tasks they need to be aware of and @mention them in the comments, so they receive alerts when the ball is in their court.
Put every project into your collaboration project management tool - Use your tool as a single source of all project-related materials and notes. This will make the material easy to find for everyone, no matter when they joined the project.
Create water cooler channels - Creating channels in your communication tools where team members can discuss non-work related topics allows them to get to know each other and be social even from afar.
Celebrate small wins - Collaboration tools are a great place to share victories, no matter how big or small. Even a short message can go a long way.
Balance the load - You can’t collaborate well if you’re overloaded with work. Use your tool’s visibility and resource management features to ensure project tasks are balanced among your team members.

Careers for iGen'ers - You Need Either Skills or Education
If you are iGen and looking for a career, please pick a major in fields where there will be plenty of jobs and avoid fields where the jobs are limited. Unless of course you are so different and truly one of a kind like: Michael Jordan, Prince, The Beatles, Albert Einstein, Bill Gates, Elon Musk, Kim Kardashian (just kidding).
You have two choices - pick a trade or get the right college education. Low skilled jobs will continue to disappear and you can not raise a family on the income from a low skilled job. You either need skills or education.
Healthcare and high tech are the booming fields now and that will continue for decades.
Thus careers in science, engineering, software, and medicine are a good choice.
There won't be many jobs for people who major in English, history, philosophy etc. Sorry.
If you want help choosing a new career, or making those big career decisions, check out my career counseling services.
Electrical Engineering and Software Engineering look really good. As does nursing, and being a family doctor.
Civil Engineering offers very few jobs since we are not building a lot of bridges and buildings. So avoid that.
Automotive engineering is tough. Not many US jobs except in the electric car field.
Jobs that must be done in person such as plumbers, electricians, barbers, beauticians, should still be in demand, although lower paying than jobs requiring a college education. The trades are more stable than many other careers.
Sales jobs will continue to shrink. Retails sales jobs are disappearing as shopping malls close and as Amazon takes over the world. Sales people are usually just middlemen. Who needs them? Sorry... However, sales people that do business development and find new customers are a different story. But the days of being a shoe salesman in a mall store are gone.
Business development and marketing are still good fields, but will see some unexpected changes.
The auto mechanic field is going to go through interesting changes with the growth of electric vehicles and self driving vehicles. EV's have less moving parts and fewer fluids to replace, but they still need tire changes.
Taxi driver jobs and truck driver jobs will start to experience less demand as automated vehicles take over. However, as of 2018, the demand for truck drivers is booming.
As automated electric vehicles take over, the need for individuals to own a car will be reduced. It will become more simple, less expensive, and more efficient to just walk outside, call up an app, have a driver-less Uber pick you up and take you to wherever you want to go. As long as a car can show up in 5 minutes or so, that will be the way to go. Owning your own car is not efficient, nor a good investment. Cars sit around doing nothing for 98% of their existence. They take up space, they consume your money on insurance and repairs even while they are just sitting doing nothing. How this will affect jobs, careers and the workplace will be interesting, and iGen'ers will be the first to experience this.
Space flight related jobs will pick up as we focus on getting people to the moon, Mars, and space stations.
Geology jobs, especially related to finding minerals on other planets should see a rise in demand.
Virtual Reality related jobs (whatever those are?) will pick up as VR technology becomes ubiquitous. Probably creating VR experiences will be popular.
The generation after the iGen'ers will be the ones who grow up thinking virtual reality is normal.
 
 

graphical user interface:
The graphical user interface (GUI  is a form of user interface that allows users to interact with electronic devices through graphical icons and audio indicators such as primary notation, instead of text-based user interfaces, typed command labels, or text navigation. GUIs were introduced in reaction to the perceived steep learning curve of command-line interfaces (CLIs), which require commands to be typed on a computer keyboard.
The actions in a GUI are usually performed through direct manipulation of the graphical elements. Beyond computers, GUIs are used in many handheld mobile devices such as MP3 players, portable media players, gaming devices, smartphones, and smaller household, office, and industrial controls. The term GUI tends not to be applied to other lower-display resolution types of interfaces, such as video games ), or not including flat screens, like volumetric displays.
User interface and interaction design:
Designing the visual composition and temporal behavior of a GUI is an important part of software application programming in the area of human-computer interaction. Its goal is to enhance the efficiency and ease of use for the underlying logical design of a stored program, a design discipline named usability. Methods of user-centered design are used to ensure that the visual language introduced in the design is well-tailored to the tasks.
The visible graphical interface features of an application are sometimes referred to as chrome or GUI (pronounced gooey) Typically, users interact with information by manipulating visual widgets that allow for interactions appropriate to the kind of data they hold. The widgets of a well-designed interface are selected to support the actions necessary to achieve the goals of users.

The classic egg drop experiment gets reinvented as a driving question for physics students to explore a real-world problem.

By Suzie Boss
July 26, 2018
When a teenager climbs atop his desk and drops an object to the floor, teacher Johnny Devine doesn’t object. Far from it—he’s as eager as the rest of the class to see what happens next.

In a split second, the student and his teammates get positive feedback for the object they have cobbled together by hand. A small parachute made of plastic and held in place with duct tape opens as planned, slowing the descent and easing the cargo to a safe landing. Students exchange quick smiles of satisfaction as they record data. Their mission isn’t accomplished yet, but today’s test run brings them one step closer to success as aspiring aerospace engineers.



To boost engagement in challenging science content, Devine has his students tackle the same problems that professional scientists and engineers wrestle with. “Right away, they know that what they are learning can be applied to an actual career,” Devine says. “Students are motivated because it’s a real task.”

From the start of Mission to Mars, students know that expert engineers from local aerospace companies will evaluate their final working models of Mars landing devices. Their models will have to reflect the students’ best thinking about how to get a payload from orbit onto the surface of the Red Planet without damaging the goods inside. While real Mars landings involve multimillion-dollar equipment, students’ launchers will carry four fragile eggs.

THE ROAD MAP

Although the project gives students considerable freedom, it unfolds through a series of carefully designed stages, each focused on specific learning goals. Having a detailed project plan “creates a roadmap,” Devine explains, “for the students to really track their progress and see how what they’re learning connects back to the guiding question: How can we successfully land a rover on Mars?”

©George Lucas Educational Foundation

Before introducing technical content, Devine wants students to visualize what space scientists actually do. By watching videos of engineers who design entry, descent, and landing systems for spacecraft, students start getting into character for the work ahead.

Devine introduces a series of hands-on activities as the project unfolds to help students put physics concepts into action. They learn about air resistance, for instance, by experimenting with parachute designs and wrestling with a real challenge: How will they slow their landers to a reasonable speed for entry into the thin Martian atmosphere?

To apply the concept of change in momentum, students design airbag systems to go on the bottom of their landers—a location aptly called the crumple zone. They experiment with bubble wrap and other materials as potential cushioners for their cargo.

As the grand finale approaches, students keep using what they learn to test, analyze, and modify their designs. “You have to repeat the equations with different trials,” one student explains. “Being able to use that math over and over again helps it stick.”

Much of the hands-on learning in this PBL classroom “might look like a traditional physics lab,” Devine acknowledges, with students learning concepts through inquiry investigations. What’s different is the teacher’s ongoing reminder “to make sure students stay in character” as systems engineers. Each lab investigation relates back to their driving question and creates more opportunities for Devine to ask probing questions and formatively assess his students’ understanding. “We do a lot of framing in and framing out after each of those lessons so students have the chance to reflect and connect it back,” the teacher explains.

EXPERT CONVERSATIONS

When it is finally time for students to launch their precious cargo off a second-story landing, engineers from local aerospace companies are standing by to assess results. How many eggs in each lander will survive the fall?

Even more important than the test data are the discussions between experts and students. One engineer, for instance, asks to see earlier versions of a team’s design and hear about the tests that led to modifications. A student named Elizabeth perks up when she hears engineers using the same technical vocabulary that she and her classmates have learned. “It was kind of a connection—this is actually a thing that goes on,” she says.

“They had really deep, meaningful conversations so that students could practice communicating their justification for their designs,” Devine says. Hearing them use academic language and apply physics concepts tells the teacher that students deeply understand the science behind their designs. “At the end of the day, that’s what I’m most concerned about,” he says.

https://youtu.be/bKc2shFqLao


 

https://www.youtube.com/watch?v=vr8pNgjI9Ig
 
new technology 
 
In technology development significant advances are as often the result of a series of evolutionary steps as they are of breakthroughs. This is illustrated by the examples of the steam engine and the computer. Breakthroughs, such as the transistor, are relatively rare, and are often the result of the introduction of new knowledge coming from a quite different area. Technology development is often difficult to predict because of its complexity; practical considerations may far outweigh apparent scientific advantages, and cultural factors enter in at many levels. In a large technological organization problems exist in bringing scientific knowledge to bear on development, but much can be done to obviate these difficulties.

Science, technology and innovation each represent a successively larger category of activities which are highly interdependent but distinct. Science contributes to technology in at least six ways: (1) new knowledge which serves as a direct source of ideas for new technological possibilities; (2) source of tools and techniques for more efficient engineering design and a knowledge base for evaluation of feasibility of designs; (3) research instrumentation, laboratory techniques and analytical methods used in research that eventually find their way into design or industrial practices, often through intermediate disciplines; (4) practice of research as a source for development and assimilation of new human skills and capabilities eventually useful for technology; (5) creation of a knowledge base that becomes increasingly important in the assessment of technology in terms of its wider social and environmental impacts; (6) knowledge base that enables more efficient strategies of applied research, development, and refinement of new technologies.

https://www.bankrate.com/investing/stock-market-basics-for-beginners/Software testing is governed by seven principles:Absence of errors fallacy: Even if the software is 99% bug-free, it is unusable if it does not conform to the user's requirements. Software needs to be bug-free 99% of the time, and it must also meet all customer requirements.Testing shows the presence of errors: Testing can verify the presence of defects in software, but it cannot guarantee that the software is defect-free. Testing can minimize the number of defects, but it can't remove them all.Exhaustive testing is not possible: The software cannot be tested exhaustively, which means all possible test cases cannot be covered. Testing can only be done with a select few test cases, and it's assumed that the software will produce the right output in all cases. Taking the software through every test case will cost more, take more effort, etc., which makes it impractical.Defect clustering: The majority of defects are typically found in a small number of modules in a project. According to the Pareto Principle, 80% of software defects arise from 20% of modules.Pesticide Paradox: It is impossible to find new bugs by re-running the same test cases over and over again. Thus, updating or adding new test cases is necessary in order to find new bugs.Early testing: Early testing is crucial to finding the defect in the software. In the early stages of SDLC, defects will be detected more easily and at a lower cost. Software testing should start at the initial phase of software development, which is the requirement analysis phase.Testing is context-dependent: The testing approach varies depending on the software development context. Software needs to be tested differently depending on its type. For instance, an ed-tech site is tested differently than an Android app.