Asquares Institute for Information Technology

Dan Allah yi mun wannan
Please take my survey!

Asquares Institute for Information Technology Survey Web survey powered by SurveyMonkey.com. Create your own online survey now with SurveyMonkey's expert certified FREE templates.

Salam
Yan'uwa ga mai bukatar Solar Muna samar da ita daga kamfanin mu na Sunking

Enlistment DSSC 2016 BATCH B
2017 NAF Recruitment
2017 NAF Recruitment Interview - BATCH 1
NAF 2017 RECRUITMENT INTERVIEW - BATCH 2
NAF 2017 RECRUITMENT INTERVIEW - BATCH 3 to 9
2017 NAF DSSC ENLISTMENT
Application Guidelines
PLEASE READ THE INSTRUCTIONS CAREFULLY

Online Registration starts on 14th January 2017 and closes on 17th February 2017.

GENERAL INSTRUCTIONS

1. Nationality: Applicant must be of Nigerian origin.

2. Age: Applicants must be between the ages of 17 and 22 years for non-tradesmen/women, 17 and 24 years for tradesmen/women by 31 December 2017. Those applying as drivers must be between the ages of 18 and 28 years by 31 December 2017.

3. Marital Status: All applicants must be single.

4. Height: Minimum height is 1.66 meters or 5.4ft for males and 1.63m or 5.3ft for females.

5. Medical Fitness: All applicants must be medically fit and meet the Nigerian Air Force medical and employment standards.

ACADEMIC/PROFESSIONAL QUALIFICATION

6. Non-Tradesmen/women: Applicants must possess a minimum of 3 credits including Mathematics and English Language in SSCE/NECO/GCE/NABTEB. In addition, applicants are also required to possess their school’s testimonials.

7. Tradesmen/women:

a. Applicants must possess ND (with minimum of Lower Credit), NABTEB, RN/RM/NCE or City & Guild Certificate.

b. Candidates with only Trade Test Certificate (including Drivers) are required to also have a minimum of 3 passes in GCE/SSCE/NECO including English Language.

Note that applicants with HND or First Degrees/Post-Graduate Certificates, University Diplomas and Grade II Teacher's certificates will not be considered for recruitment as airmen/airwomen into the Nigerian Air Force and should not apply.

8. Attestation Forms: Applicant's attestation form must be signed by a military officer from the same state as the applicant and not below the rank of Squadron Leader or equivalent in the Nigerian Army and the Nigerian Navy, and Police Officer of the rank of Assistant CP and above. Local Governments Chairmen/Secretaries, magistrates and principals of government Secondary Schools from applicants' state of origin can also sign the attestation forms. The signees passport photograph and either photocopy of drivers licence or international passport must be attached. In addition, applicants are to bring with them Local Government Indigene Certificate to the Zonal Recruitment Centers and final selection interview.

9. Requirements: Applicants are advised to carefully read the requirements below before filling the form:

a. Medical Records: ND Medical Records.

b. Nursing: RN-RM.

c. Lab Technician: ND Medical Lab Science.

d. X-Ray Technicians: ND X-ray Technology.

e. Dental Technician: ND Dental Technology/ Dental Therapy.

f. Pharmacy Technician: ND Pharmacy Technology.

g. Environmental Technician: ND Environmental Technology.

h. Biomed Technician: ND Biomed Technology.

i. Optometry Technician: ND Optometry Technology.

j. Statistics: ND Stats.

k. Assistant Chaplain: ND Christian Religious Study.

l. Assistant Imam: ND Arabic/Islamic Studies.

m. Engineering Technicians: ND Mechanical Engineering/Electrical Electronics Engineering /Air Engineering Technology.

n. Meteorologist: WMO Class III Meteorology Assistant Certificate, Certificate in ATCA/Base Operator, and Fire.

o. Domestic Electricians: ND Electrical Electronics, ND/Trade Test Certificate 1,2,3 Domestic Electrician, Works.

p. Building Technology: ND Building Technology/Quantity Surveyor/ Land Surveying/ Civil Engineering.

q. Public Relations/Info: ND Mass Communication/Trade Test Certificate in Videography/Photography.

r. Secretarial Assistants: ND Office Technology Management.

s. Library Assistants: ND/NCE Library Science.

t. Music: ND Music. In addition, playing experience in any recognised Band will be an advantage.

u. Driver/Mechanic: Trade Test and current driver's license with practical experience.

v. Works: Trade Test Cert in Welding/Carpentry/Painting/Sign Writing/Plumbing/Mason/Domestic Electrician/Refrigeration and Air Conditioning/Tailors.

w. Computer/Space Tech: ND/Computer Hardware Engr/Tech, Software Engr/Tech, Satellite Image Interpreter/GIS Tech, SatCom Hub Installation Tech, Fiber Optic Tech, Network Tech, Cyber Security Tech, Web Designer/Master and Software Developer. Possession of recognized certifications will be an advantage.

x. ND Physiotherapy

y. ND Medical Supply

z. Sports: Certificate of participation/Medals in National and International sporting competitions and in addition ND/NCE Physical Education can be an added advantage.

aa. Catering: ND Catering Services/Catering Certificate.

ab. Education: NCE Physics, Chemistry, Biology, Mathematics, English, Home Economics, Nigerian Languages, French, Business Management, Fine Art, Basic Science/Integrated Science, Computer Secience, Music, Technical Education/Basic Technology, Christian Religious Knowledge, Islamic Regligious Knowledge.

QUALIFYING RECRUITMENT TESTS

10. Qualifying Recruitment Tests will hold in the following Centers:

a. Makurdi: Nigerian Air Force Base, Makurdi.

b. Ilorin: 303 MAG - Nigerian Air Force, Ilorin.

c. Lagos: Sam Ethnan Air Force Base, Ikeja – Lagos.

d. Enugu: 155 Nigerian Air Force Base, Enugu.

e. Port-Harcourt: 115 Special Operations Group, Nigerian Air Force, Port-Harcourt.

f. Benin: 107 Air Maritime Group, Nigerian Air Force Benin.

g. Kaduna: Nigerian Air Force Base, Kawo – Kaduna.

h. Kano: 403 Flying Training School, Kano.

i. Maiduguri: 105 Composite Group Nigerian Air Force Base, Maiduguri.

j. Ipetu-Ijesha: 209 Quick Response Group, Ipetu-Ijesha.

k. Sokoto: 119 Forward Operation Base Mabera, Sokoto.

l. Yola: 103 Strike Group, Nigerian Air Force, Yola.

m. Jos: 451 Nigerian Air Force Station, Jos.

n. Bauchi: 251 Nigerian Air Force Base, Bauchi.

WHAT IS A HACKATHON ANYWAY?
A hackathon is a period of continuous time (more than
one day) in which a team focuses their effort on
innovation rather than on their normal day-to-day
routine. That description is full of important pieces so
let’s break it down.
WHO?
You may be tempted to compare this to “20% time” at
Google, which allows individuals to spend some
percentage of their time per week on their own personal
initiatives, or a company-wide Innovation Day, which is
heavily facilitated and involved many employees from
many teams. While these models provide value, I am
referring to a hackathon executed at the team level.
For this to be most successful, your team should have a
fairly high level of autonomy so that you can install new
software, drive your own initiatives, and even configure
infrastructure on demand. The “Autonomous Team,” in
which a team of developers, analysts, and testers fully
own the delivery of a project while working directly with
product stakeholders, has proven to be an effective way
to deliver software. Enterprises often suffer from slow-
moving processes and top-down thinking, but the
Autonomous Team can iterate and innovate on their
own ideas. Hackathons can help teams to cultivate and
maintain an innovative spirit.
WHAT?
What a team works on during a hackathon is
completely up to the team. So anything goes right? It’s
all about creativity and thinking outside the box, right?
Well… not quite. We must remember that the hackathon
is happening in a business during working hours.
Therefore, we need to strike a balance between personal
gain and business value — with the scale tipping more
towards the latter. It is important to consider multiple
dimensions such as “How long will it take to finish this
project?” or “How much value could it provide to the
team?” when deciding to dedicate time to a specific
project or idea during a hackathon. This analysis could
be done many different ways. See the “Tips & Tricks”
section below for more info.
For example, a successful project from my last
hackathon was the “Easy Deployment Button,” a
physical button you could press to trigger a
deployment. The perceived team and business value at
first was fairly low, but after exploring the idea, we
realized that it was an excellent demonstration of the
powers of automation over manual steps. A literal one-
press deployment was possible. On the other hand, the
fun factor of this project was super high. It involved
electronics, software, and even a bit of soldering in the
office!
HOW LONG?
Time is a crucial factor for a successful team
hackathon. It should be run as a multi-day event. Shoot
for the three to five day range. When an individual or a
group only has a single day to work on something
significant, they may not be able to achieve much…
especially when experimenting with something new. But
when given a few days, you have time to learn,
experience some trial and error, and are more likely to
come out with a polished prototype or working
software. One or two days just is not enough time.
It’s highly unlikely that the stars will align perfectly so
that all deadlines will magically dissolve so that your
teams can devote an uninterrupted week to a
hackathon. Putting it on the schedule early and planning
for it is your best bet to actually make it happen. Avoid
thinking of a hackathon as something that will only eat
time away from hitting your tight deadlines. Instead, it is
something that you build into your schedules that will
help your team to deliver a better product faster. Keep
the long term gain in mind.
WHY?
Hackathons engender innovation. Everything about it,
from ideation to implementation, encourages the team
members to be creative. This isn’t something we get to
do everyday. As such, a time to bring creative energy
into the team and focus it on the organization gives
people a chance to flex their brains in new ways.
Hackathons give space for a single person to focus on
a single idea all the way through to completion. On an
agile team, ideas may come from customer feedback,
and then analyzed, designed, coded, and tested by four
different people. By giving someone the power to
control that entire flow from ideation to completion, not
only do they experience a deeper sense of
accomplishment, but they also get a more holistic view
of the development process.
Hackathons promote cross-pollination of roles . A big
anti-pattern is to think that hackathons are for
developers only. This is a team event! Everyone on the
team should participate. During a recent hackathon we
had a User Experience Designer pairing with a
Developer redesigning the application as mobile-first,
and a Business Analyst pairing with an Iteration
Manager figuring out how to improve the customer
community interactions! Afterwards, they spoke of how
the different perspectives each person brought to the
table really helped make their projects fun and a
learning experience.
Hackathons add tangible value to the organization. The
most obvious tangible output from your team’s
hackathon is the projects. While it’s unlikely that your
hackathon projects will be production-ready by the end,
look to turn your hacks into full-fledged production
solutions. This not only adds tangible value to the
organization’s software, but is also a pretty big morale
boost for your employees to see their ideas recognized
and providing value.
The less obvious (but more important) output is
the process and growth of the team. For a few weeks
after the last hackathon I participated in, the team was
on a bit of a high. We knew what we could accomplish
some amazing things when we put our minds to it. We
saw how creative our teammates were. As we returned
to business as usual, we had a renewed enthusiasm in
working together as a team and delivering awesome
software. And we have already started planning the next
hackathon.
TIPS & TRICKS
Here are a few practical tips I learned along the way to
help make your team hackathon a success. Use them
or put your own spin on them. Remember, its a
hackathon so be creative!
Consider using “sliders” (or just thinking about
them) as a way of visualizing the aspects of a
project idea when deciding if its something you
want to do during the hackathon. For example:
Time — How likely is it that someone on my team
can “complete” (used loosely here) this hack during
the hackathon? Team Value — How much value
could this hack provide to the team/
project? Business Value — How much value could
this hack provide to the organization as a
whole? Excitement — There is an aspect of fun in a
hackathon. How “exciting” is the hack? (New
technologies, brand new ideas, etc)
When thinking of ideas, consider grouping them
into categories such as Tech Hacks, Design Hacks,
or Non-Tech Hacks. These categories are not
intended to segregate roles, but merely to highlight
the various options. Any role can work on any
hackathon project with anybody else.
Immerse yourself and your team into the activity at
hand. During the hackathon, try to minimize
context switching and devote as much time and
energy as you can into your projects. Maybe this
means skipping normally scheduled team meetings
such as stand up or sprint planning. Maybe this
means blocking off calendars and pushing back
external meetings.
Make the hackathon fun ! Make t-shirts. Get the
whole team involved in organizing. Order food.
Play music. Celebrate with opening and closing
ceremonies.
Don’t let your hackathon happen inside a
box. Share the learnings with the
organization. Internal blogs, mailing lists, or lunch-
and-learns are all great ways to spread the news.
Showcase the outputs and cool things your team
built, but don’t let that be the focus. Instead, shift
focus to your team’s learnings and encourage
others to have their own hackathons.

A male child is more important than a female child. In many cultures, a male child is more important than a female child. A male child will carry the family name, and his children will have the same last name. If a family only has a daughter, the family name will die out. Also, a son can be an heir to the father. In many countries, a daughter cannot do this.

Asquares Institute for Information Technology welcome my friend to the new future which included some part of our life and it's security to you an

try to search us
http://a2slinkedin.mywapblog.com

https://plus.google.com/collection/oNO-LB

Are You Ready to Wear Your Own Device (WYOD) in 2016?
December 30, 2015 • 9,017 Views • 1,144 Likes • 103 Comments

For IT administrators it has never been so complex yet interesting. Until about 6-8 years ago, mobility in workforce meant supporting company equipment such as corporate designated laptops and Blackberry phones. And it worked - IT organizations and employees realized the power of mobility and how having corporate mobile assets enhanced their productivity. Over the past several years there has been a proliferation of mobile devices and consumers have choice and in many cases have multiple devices at their disposal. I personally have both iOS and Android devices in different form-factors for personal and family use. And then I have my super durable workhorse laptop and a smartphone from my company. As other techies, I can justify the existence of each of them :)

Proliferation of Smartphones

Earlier this year, IDC forecasted Smartphone growth being the fastest with slower growth in the PC and tablet markets. As per IDC, "Detachable 2-in-1s show strong growth potential in tablets, and convertible notebooks are beginning to gain traction in PCs. But ultimately, for more people in more places, the smartphone is the clear choice in terms of owning one connected device." I am sure PC manufacturers will want to argue with such forecast but it is a growing reality. All you need to do is look around you at an airport, train station or any public place - Smartphones are everywhere. I am pretty social media savvy and mostly get my news, linked-in, twitter feeds on my Smartphone. Enterprise IT organizations have been keenly observing the growth of Smartphones and some of them see an opportunity in this paradigm.

Bring Your Own Device (BYOD)

In 2009-10 timeframe, BYOD emerged as an enterprise IT initiative to allow employees and partners to use a personal purchased device of choice e.g. a Smartphone and access applications authorized by IT. As expected, IT organizations were not thrilled initially as there were concerns around security, upgrades etc and general complexity in managing these devices. However the benefits of BYOD overweigh the complexities. Besides cutting costs of devices, enterprises can now expand their mobile workforce and enhance productivity. Most new applications including CRM etc are developed in a 'mobile first' and 'cloud first' environment and enterprise IT can help the workforce access these applications faster through BYOD and focus less on qualifying and supporting a new corporate owned mobile device. It also means the significance of cloud increases greatly as a medium to deliver these applications. Microsoft, VMware etc are all trying to enable the new 'Cloud-Smartphone' ecosystem. BYOD adoption is increasing and as per Gartner in a May 2015 press release - by 2017, half of employers will require employees to supply their own device for work purposes. Pretty bold statement! Assuming BYOD gets adopted at the rate Gartner predicts, what's next enterprise IT needs to prepare for?

Wear Your Own Device (WYOD)

WYOD is not a widely used term and some can argue it is a subset of BYOD - regardless it is something that cannot be ignored. The significance of WYOD is in extending use cases beyond IT providing/allowing access to enterprise and consumer applications. WYOD is about enabling Internet of Things (IoT) use cases. Commercially, there are many applications in healthcare, military, supply-chain, factories etc that can benefit from WYOD. While the first Google Glass wasn't a commercial success, next generation of such devices combined with fast, affordable and reliable wireless connectivity, ease of use and new IoT applications will drive greater adoption. Apple Watch, Fitbit and other wrist wearable devices are already being used for smarthome and personal health applications. We will see growth in commercial adoption as developers write new IoT applications for wearables.

Wearable technology adoption is surely on the rise and while it is not forecasted to be faster than Smartphones, this category is emerging as the next biggest connected device category. IDC is forecasting 155.7 million units to be shipped in 2019. And a lot of us will be wearing these. In full disclosure, I don't have a wearable device on me but I am sure I will find a justification to own one in 2016 :)

How about you? Are you going to Wear Your Own Device (WYOD) in 2016? If you're in IT, are you going to incorporate WYOD in your portfolio?

As always, would love your comments.

About the Author

Pranay Prakash is the Vice president of Product Management/Marketing at Tridium at Honeywell responsible for M2M and IoT software and hardware products. He is extremely passionate about cloud and is focused heavily on making Internet of Things (IoT) a reality. He believes cloud has become a lot bigger and moved beyond traditional IT devices.

Connect with Pranay at: Twitter: ://twitter.com/prakash_pranay; LinkedIn:http://www.linkedin.com/pub/pranay-prakash/0/542/717

Information Technologies LinkedIn